HL7_Version_3

nullHL7 Version 3HL7 Version 3Veli BICERAgendaAgendaHL7 Problems with Version 2.x HL7 Models Use Case Model Information Model Interaction Model Message ModelHL7HL7founded in 1987 To provide standards for the exchange, management and integration of data that supports clinical patient care and the management, delivery and evaluation of healthcare services.Problems with version 2.xProblems with version 2.xProblem: misunderstanding of specifications Result: Different implicit information models Problem: Misleading conformance claims Result: No vocabulary to describe conformance conceptsProblems with version 2.xProblems with version 2.xImplicit information model, not explicit Need for controlled vocabularies No explicit support for object technologies No explicit support for security functions Optionality is ubiquitous and troublesomeContents of HL7 V2.3Contents of HL7 V2.3Trigger events Actions or occurrences Messages Information content Segments Repeating structures Data elements Data representationHL7 Version 3.X SpecificationHL7 Version 3.X SpecificationVersion 3 Methodology - MDF Conformance Claims to improve the internal consistency of HL7 HL7 ModelsHL7 ModelsA model is a collection of subject areas, scenarios, classes, attributes, use cases, actors, trigger events, interactions, etc. that depict the information needed to specify HL7 Version3 messages. HL7 models are further divided into four specific models - a use case model, an information model, an interaction model, and a message design model.nullHL7 ModelsnullUse Case ModelUse Case ModelUse Case ModelDescribes specific situations in which communication between healthcare entities is needed. nullInformation ModelInformation ModelInformation ModelA detailed and precise definition for the information from which all data content of HL7 messages are drawn. Classes, Attributes, and Relationships Documented in the Reference Information Model, the Domain Information Model, and the Message Information Model State Transition Models for certain selected classes. Data Types and Constraints. Reference Information Model (RIM)Reference Information Model (RIM)Root of all information models. Provides a static view of the information. A HL7-wide common reference model that integrates all Technical Committees’ domain views. Committees and SIGs generally work with a small subset of the RIM - called Domain Information Model or DIM.Reference Information Model (RIM)Reference Information Model (RIM)Foundation Classes Acts Entities Roles Communication Infrastructure Core Infrastructure Message Communications Control Structured DocumentsReference Information Model (RIM)Reference Information Model (RIM)Reference Information Model (RIM)Reference Information Model (RIM)Reference Information Model (RIM)Reference Information Model (RIM)nullInteraction ModelInteraction ModelInteraction ModelSpecifies all Trigger Events and Message Flows. Specifies the Application Roles. Interaction ModelInteraction ModelEach Interaction consists of: Trigger event Initiators of Interactions. Message ID Each interaction sends one particular message Sender role When trigger event detected, message is sent Receiver role Receiver responsibilityInteraction ModelInteraction ModelInteractionInteraction ModelInteraction ModelnullMessage ModelMessage SpecificationMessage SpecificationSubset the RIM  MIMSubset the RIM  MIMThe RIM must first be refined by subsetting and constraining it Create a MIM with RIM classes needed Develop an R-MIM from these classes Collection of classes with some constraints Collection of attributes and associations to support the R-MIM nullConvert the MIM  R-MIMConvert the MIM  R-MIMConstrain cardinality on Associations Constraints on Attributes Some may be left out Sub-components may be individually constrained Classes are duplicated for different uses May modify the Inheritance structure Some specializations may subsume the generalization Always inherit downwards to specializations nullMIMnullRMIMnullnullnullImplementation Technology SpecificationImplementation Technology SpecificationA method of encoding and sending HL7 messages. XML represents one of several ITS to be developed An HL7 V2.3 MessageAn HL7 V2.3 MessageMSH|^~\&|LABGL1||DMCRES||199812300100||ORU^R01|LABGL1199510221838581|P|2.3 |||NE|NE PID|||6910828^Y^C8||Newman^Alfred^E||19720812|M||W|25 Centscheap Ave^^ Whatmeworry^UT^85201^^P||(555)777-6666|(444)677-7777||M||773789090 OBR||110801^LABGL|387209373^DMCRES|18768-2^CELL COUNTS+DIFFERENTIAL TESTS (COMPOSITE)^LN|||199812292128||35^ML|||||||IN2973^Schadow^Gunther^^^^MD^UPIN ||||||||||^Once||||||CA20837^Spinosa^John^^^^MD^UPIN OBX||NM|4544-3^HEMATOCRIT (AUTOMATED)^LN||45||39-49 ||||F|||199812292128||CA20837 OBX||NM|789-8^ERYTHROCYTES COUNT (AUTOMATED)^LN||4.94|10*12/mm3 |4.30-5.90||||F|||199812292128||CA20837null <_StkhldrAffltn> …nullnullnullnull           - - - -         - -     - -   …..Thanks for your attentionThanks for your attention