100 likes | 254 Views
HL7 version 3. Special Topic: User Interfaces. Scope: UI components, binding to v3 model. Slide contents published under the Creative Commons / Attribute-Share Alike license Source: www.ringholm.de/download/HL7v3_implementation.zip. UI. PL. RIMBAA Technology Matrix. Processing Logic.
E N D
HL7 version 3 Special Topic: User Interfaces Scope: UI components, binding to v3 model Slide contents published under the Creative Commons / Attribute-Share Alike license Source: www.ringholm.de/download/HL7v3_implementation.zip
UI PL RIMBAA Technology Matrix Processing Logic Object Representation User Interface
User Interfaces • There are two (extreme) options: • Run time: Dynamically (at run time) generate the UI based on a CIM/LIM-like definition • need to do some pre-formatting, otherwise the generated layout may be quite nonsensical for the human user • Development time: Define the UI first; bind elements in the UI to RO/CO/AO classes/attributes.
User Interface - Development • UI integration with templates (LIM): commonality is one of the key reasons for using RIM • start with the generic controls, make them work, bolt them together, less generic as you go up the data stack.
Model Driven User Interfaces • HL7 version 3 has an elaborate terminology model. • Based on HL7 (and ISO) data types Person name: EN [0..*] administrativeGenderCode: CE … Person Demographics Sex: CE data type: (code, codeSystem) OR (nullFlavor)
User Interface Implementation Experiences Slide contents published under the Creative Commons / Attribute-Share Alike license Source: www.ringholm.de/download/implementation_mechanics.ppt
CfH NHS - Xforms • https://xmlprocess.projects.openhealthtools.org/ • Annotated MIF to Xform generator. • Annotations: • Parts that should be editable or read-only or hidden • Use business names instead of formal RIM names as that might make things a bit more intuitive to users
Any Questions ? • Or: post your question/suggestions via • HL7 Wiki: http://bit.ly/d7tSsL • E-mail v3impl@ringholm.com