surely the obvious approach is that the stored field contains the UCUM case-sensitive code, and that applications / services use UCUM tables to render whatever display form is asked for in a client call? (I realise openEHR archetypes are not doing this; they should be...)

there's another problem: in both v2 and CDA, HL7 specified a single units field on the assumption that implementers could somehow square the circle and have a single units that satisfies human and computer readability. This is not possible. Hence the mess we are in.




_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Reply via email to