You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: