Thomas wrote: William, what is a "true" XML message? I would love to know. We have already provided a powerful language and tools for the job you are doing. Why don't you use them?
- thomas beale William's answer (rest to follow later, need the message in different system to work on due to netuse): Sorry about the 'true'. I mean the HL7 v3 messages ready but not completely filled with content. Why I do not use the OpenEHR tools? That is easy, OpenEHR tools currently do not support the incusion of archetypes in HL7 v3 messages. The long list of artifacts is meant for use in the EHR and HL7 v3 messages in a standardized format content and relationships between variables. So much easier will it not be, the pink boxes are left more and more for OpenEHR style generic items, e.g. for scale representation and vital function representation. Work in HL7 is going the same way as you describe. Datatypes is ongoing work at ISO level, yes not all solved but many are. But I have to deliver the clinical content to fit in the national IT infrastructure. That is why I ask for tools that do one representation and allow both HL7 v3 and OpenEHR technological instantiation. A to B is doable, B to A not. William - If you have any questions about using this list, please send a message to d.lloyd at openehr.org
