-
Notifications
You must be signed in to change notification settings - Fork 34
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
Define nomenclature for use in Observation model #41
Comments
I think we should also look at this: I believe this is the most widely used and comprehensive standard. I can't find the details of this yet, but what about this for Unit of measure? |
For observation type, we should also consider LOINC code as defined by FHIR: |
FHIR recommends this for UOM: UCUM - http:https://unitsofmeasure.org/ucum.html |
Fields such as Reading.readingType and Reading.uom will generally be populated with the same subset of values.
Take for example he Reading.readingType attribute, which describes the type of reading that was observed. One of the challenges we have is that different ingest services are free to different spellings to specify the same reading type. For example, you may get "ECG Lead I", "ecg_lead_I", "lead I", etc.
We should adopt a standard nomenclature for the Streams Healthcare Analytic Platform to be used when specifying the values for these types. Analytic applications will likely rely on the value set by this attribute to determine the type of analysis to run. Likewise, visualization applications may use this value to generate the graphs. In short, this will help to promote interoperability between services and applications.
We can start by looking at ISO 11073 and PCD Profile Rosetta Terminology Mapping for guidance on how to define this nomenclature.
https://en.wikipedia.org/wiki/ISO/IEEE_11073
http:https://wiki.ihe.net/index.php/PCD_Profile_Rosetta_Terminology_Mapping
The text was updated successfully, but these errors were encountered: