Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FHIR DSTU3 issue #46

Open
Brycert opened this issue Apr 5, 2017 · 0 comments
Open

FHIR DSTU3 issue #46

Brycert opened this issue Apr 5, 2017 · 0 comments

Comments

@Brycert
Copy link

Brycert commented Apr 5, 2017

Hello,

Our organization just went from DSTU2 to DSTU3. In the DSTU2 version the encounter object has a method "class_" that accepts an enumeration of consisting of states of the patient such as "Inpatient", "Outpatient","Ambulatory", etc... The DSTU3 version has modified the class_ method to take a Coding object that consists of a CodeID(string) and DisplayText (string). So the question is, with the enumeration gone, how are the states to be persisted in this Coding object? We certainly cannot rely on a string for determining state as there may be a plethora of fat fingered patient states hydrating the object.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant