Presentation is loading. Please wait.

Presentation is loading. Please wait.

1 HL7 Version 3 at NCICB Overview  Session Details  Introduction  Reference Information Model (RIM)  HL7 Modeling Conventions  HL7 Process & Artifacts,

Similar presentations


Presentation on theme: "1 HL7 Version 3 at NCICB Overview  Session Details  Introduction  Reference Information Model (RIM)  HL7 Modeling Conventions  HL7 Process & Artifacts,"— Presentation transcript:

1 1 HL7 Version 3 at NCICB Overview  Session Details  Introduction  Reference Information Model (RIM)  HL7 Modeling Conventions  HL7 Process & Artifacts, Vocabulary & Data Types  HL7 Version 3 at NCI  Web Resources

2 2 Session Details  Target Audience: – Developers and Analysts – Adopters  Prerequisites: – Modeling concepts

3 3 Session Details: Presenters and Participants   Who is in attendance? – Name – Title – Cancer Center – Reason for Attending Note: This training can also be used as a self-paced training. (See notes for each slide)

4 4 Session Details : Training Objectives  Objectives of this training are to: – Provide an overview of HL7 version 3 – Define terms and concepts used in HL7 – Describe the HL7 modeling methodology – Introduce reason for HL7 version 3 at NCICB

5 5 Introduction  In this section, we will: – Introduce the HL7 organization and the version 3 standard – Discuss the goal of HL7

6 6 Introduction: What is HL7?  Heath Level Seven (HL7) is an ANSI-accredited Standards Developing Organization (SDO) operating in healthcare arena  Provides standards for data exchange to allow interoperability between healthcare information systems  HL7 focuses on the clinical and administrative data domains  It is a not-for-profit organization made up of volunteers – providers, payers, vendors, government  Key goal is syntactic and semantic interoperability

7 7 Introduction: 4 Pillars of Semantic Interoperability The 4 pillars of semantic interoperability are: 1.A common Reference Information Model (RIM) spanning the entire clinical, administrative and financial healthcare universe 2.A well-defined and tool-supported process for deriving data exchange specifications ("messages") from the RIM 3.A formal and robust Data Type Specification upon which to ground the RIM 4.A formal methodology for binding concept-based terminologies to RIM attributes.

8 8 Reference Information Model (RIM)  In this section, we will: – Discuss the modeling concepts used in HL7 Version 3 – Describe the Backbone Classes of the HL7 RIM

9 9 Reference Information Model (RIM): Overview Reference Information Model (RIM):  Follows object oriented developmental methodology based on a UML model  The fundamental model from which all v3 messages are derived is referred to as the Reference Information Model (RIM)  The RIM is a generic, abstract model that expresses the information content of all the areas of healthcare  Defines all the information from which the data content of HL7 messages are drawn  Forms a shared view of the healthcare domain and is used across all HL7 messages independent of message structure

10 10 Reference Information Model (RIM): Backbone Classes A physical thing, group of physical things or an organization capable of participating in Acts, while in a role. A record of something that is being done, has been done, can be done, or is intended or requested to be done. A competency of the Entity playing the Role as identified, defined, guaranteed, or acknowledged by the Entity that Scopes the Role. An association between an Act and a Role with an Entity playing that Role. Each Entity (in a Role) involved in an Act in a certain way is linked to the act by one Participation-instance. Entity RoleParticipationAct A connection between two roles expressing a dependency between those roles. A directed association between a source act and a target act. Role Link Act Relationship n n

11 11 Reference Information Model (RIM) Backbone Class: Entity Entity classCode : CS determinerCode : CS id : SET code : CE quantity : SET name : BAG desc : ED statusCode : SET existenceTime : IVL telecom : BAG riskCode : CE handlingCode : CE Entity: a person, animal, organization or thing A collection of classes related to the Entity class, its specializations and related qualifying classes. The classes represent health care stakeholders and other things of interest to health care. Entity has the following sub-classes: Container Device LanguageCommunication LivingSubject ManufacturedMaterial Material NonPersonLivingSubject Organization Person Place

12 12 Reference Information Model (RIM): Backbone Class: Role Role classCode : CS id : SET code : CE negationInd : BL addr : BAG telecom : BAG statusCode : SET effectiveTime : IVL certificateText : ED quantity : RTO positionNumber : LIST... Roles: A responsibility or part played by an entity (e.g. Person in a role of patient, employee, etc.) – different faces of an Entity A collection of classes related to the Role class and its specializations. These classes focus on the roles participants may play in health care. Role has the following sub-classes: Access Employee LicensedEntity Patient

13 13 Reference Information Model (RIM): Backbone Class: RoleLink RoleLink typeCode : CS effectiveTime : IVL Role 0..n outboundLink 0..n source 0..n inboundLink 0..n RoleLink: A connection between two roles expressing a dependency between those roles. RoleLink has no sub-classes.

14 14 Reference Information Model (RIM): Backbone Class: Participation Participation typeCode : CS functionCode : CD contextControlCode : CS... sequenceNumber : INT negationInd : BL noteText : ED time : IVL modeCode : CE awarenessCode : CE signatureCode : CE signatureText : ED performInd : BL substitutionConditionCode : CE Participation: An association between an Act and a Role with an Entity playing that Role. Participation has the following sub-class: ManagedParticipation

15 15 Reference Information Model (RIM): Backbone Class: Act Act classCode : CS moodCode : CS id : SET code : CD negationInd : BL derivationExpr : ST text : ED title : ST statusCode : SET effectiveTime : GTS activityTime : GTS availabilityTime : TS priorityCode : SET confidentialityCode : SET repeatNumber : IVL interruptibleInd : BL levelCode : CE independentInd : BL uncertaintyCode : CE reasonCode : SET languageCode : CE Act: A collection of classes including the Act class and its specializations. These relate to the actions and events that constitute health care services. A record of something that is being done, has been done, can be done, or is intended or requested to be done. Act has the following sub-classes: Account ControlAct DeviceTask DiagnosticImage Diet FinancialContract FinancialTransaction InvoiceElement Observation Participation PatientEncounter Procedure PublicHealthCase SubstanceAdministration Supply WorkingList Note: Sub-classes also include Core Infrastructure, Message Communications Control and Structured Documents classes not shown here.

16 16 Reference Information Model (RIM): Backbone Class: ActRelationship ActRelationship typeCode : CS inversionInd : BL contextControlCode : CS contextConductionInd : BL sequenceNumber : INT priorityNumber : INT pauseQuantity : PQ checkpointCode : CS splitCode : CS joinCode : CS negationInd : BL conjunctionCode : CS localVariableName : ST seperatableInd : BL Act 0..n outboundRelationship 0..n source inboundRelationship 0..n target 1 ActRelationship: A directed association between a source Act and a target Act. A point from a later instance to a earlier instance OR point from collector instance to component instance. ActRelationship has no sub-classes.

17 17 Reference Information Model (RIM): The Complete RIM Domain Related Infrastructure Related Structured Documents

18 18 Reference Information Model (RIM): RIM-UML Instance Scenario John DoePatientSubject EntityRoleParticipationAct Dr. Smith HealthCare Provider Surgeon* John DoePatientSubject Has Pertinent Information Act Relationship (Clinical Trial Act) Protocol ECOG 1112 XYZ Hospital HealthCare Facility* Location (Procedure Act) Prostectomy

19 19 HL7 Version 3 Process & Artifacts  In this section, we will discuss: – Domain Message Information Model (DMIM) – Refined Message Information Model (RMIM) – Hierarchal Message Definitions (HMDs) – Message Type (MT)

20 20 HL7 Version 3 Process & Artifacts: Overall Process RIMD-MIM R-MIM 1..* HMD MT 1..*

21 21 Entry points HL7 Version 3 Process & Artifacts: Examples Arrows Color-coding Labeling Directional

22 22 Reference Information Model (RIM): HL7 Modeling Conventions  Color-coding – colors of classes in the model denote the type of backbone class to which it belongs  Arrows – Participations, ActRelationships and RoleLinks are directional arrows that have rather than being lines that connect classes like in UML  Entry points – where to start reading the model; DMIMs have one or more entry points, RMIMs have one  RMIMs are directional – all associations flow out from the entry point to the remaining parts of the model  Labeling – associations in RMIMs are labeled on the distal end only

23 23 HL7 Process & Artifacts: Domain Message Information Model (DMIM) A DMIM is a refined subset of the RIM that includes a set of class clones, attributes and relationships that can be used to create messages for a particular domain (a particular area of interest in healthcare).

24 24 HL7 Process & Artifacts: Refined Message Information Model (RMIM) The RMIM is a subset of a DMIM that is used to express the information content for a message or set of messages with annotations and refinements that are message specific.

25 25 HL7 Process & Artifacts: Hierarchal Message Definitions (HMDs) A Hierarchal Message Definition (HMD) is a serialized version of the RMIM in a specific order.

26 26 HL7 Process & Artifacts: Message Type (MT) The Message Type elements and attributes in an XML message instance correspond to the sequence of data in the HMD

27 27 Vocabulary & Data Types  In this section, we will discuss: – HL7 Standard Vocabulary Structural Attributes – prescribed HL7 vocabulary Non-Structural Attributes – vocabulary chosen by organization – Robust Data Types

28 28 Vocabulary & Data Types: Structural Attributes Structural attributes are used to specify type and state of each RIM class and what it means when used in a message. They use a standard vocabulary defined and controlled by HL7. An Act of the Class Observation (OBS) with a Mood of Event (EVN). classCode and moodCode are both Structural Attributes

29 29 Vocabulary & Data Types : Non-Structural Attributes  Other attributes don’t have an assigned vocabulary  Organizations can choose any industry standard vocabulary  For example, commonly used ones for Observation Acts are LOINC, SNOMED, MedDRA, etc.  Must specify more than just the code value, other data is needed for semantic interoperability…this is where data types come in

30 30 Vocabulary & Data Types : Data Types What is a data type? lengthOfStayQuantity is attribute of the EncounterProcess class. lengthOfStayQuantity has a data type of Physical Quantity (PQ).

31 31 Vocabulary & Data Types : Data Types  Data types in HL7 version 3 are complex  Each data type has attributes  Each attribute has a data type of its own Physical Quantity (PQ) example The attributes ‘value’ and ‘unit’ are part of the complex data type Physical Quantity (PQ). Value is expressed as the data type of integer (int).

32 32 HL7 Version 3 at NCICB  In this section, we will discuss: – Why HL7 at NCICB? – NCICB Clinical Architecture Vision – caAdapter

33 33 HL7 Version 3 at NCICB: Why HL7?  Recommended by the Health and Human Service (HHS) as the messaging standard for electronic exchange of clinical data.  Over 90% of US hospitals have implemented some version of 2.x HL7 messages.  Support for translational research requires integration of research data with the clinical data. – V3 offers the syntactic and semantic interoperability to make this possible

34 34 HL7 Version 3 at NCICB: NCICB Clinical Architecture Vision HL7 version 3 supports messaging within the NCICB Clinical Architecture Vision. etc. Tissues Labs JDBC 2 Analytical Applications Analytical and Reporting Tools (SAS, WebSDM, ToxViewer, I- Review, etc.) Ad Hoc Query Tool BIO- gopher Master Index Message Exchange Services (ebXML) Translation Service (CAM/caAdapter) Electronic Medical Record (EMR) HL7 v3 Excel, Text, HL7 v2, etc. HL7 v3 HL7 Transactional Database (HTB) Extensions (CDUS/CTM S) Base Janus Model BRIDG Clinical/Clinical Trials Applications C3D caMATC H C3PRSAE Study Specific Analysis Data Clinical Data Sources Patient Identifiable Clinical Environment caGRID caBIG HL7 v3 Secure Transport Between Sites caBIO/CTOM HL7 RIM BRIDG caBIO/CTOM HL7 RIM FDA SPONSOR CTEP DCP Other External Agencie s HL7 v3 Common Security Module (CSM)Enterprise Vocabulary Service (EVS)Data Standards Repository (caDSR) Secure Transport Between Sites Excel, Text, HL7 v1, v2, etc. De-Identification/ Re-Identification Service HL7 v3 eCTD, Excel, Text, HL7 v2, etc. Translation Service (CAM/caAdapter) HL7 v3 caPRI FIREBIRD CRIX Data Repository

35 35 HL7 Version 3 at NCICB: Highlights of the NCICB Clinical Architecture Vision  caAdapter – Open source toolkit which facilitates v3 message building, parsing and validation  Message Exchange – Service supporting message transmission and routing  HL7 Transactional Database - HL7 RIM-based transactional database and data access service  De-identification Service – Service for de-identifying patient information from HL7 messages  Analytical Applications - Applications for querying, reporting, mining clinical data  Cancer Data Standards Repository (caDSR) - Shared metadata repository  Enterprise Terminology Services (EVS) - Terminology service for hosting controlled vocabulary, including HL7 registered terminology

36 36 HL7 Version 3 at NCICB: caAdapter  Facilitates the building, parsing, and validation of HL7 v3 messages  Components include: – HL7 v3 Message Parser – parses HL7 version 3 messages to RIM object graph – HL7 v3 Message Builder – builds HL7 version 3 messages from the RIM object graph – HL7 v3 Artifacts – implements RIM objects, data types and metadata objects – Metadata Loader – represents HL7 version 3 metadata in-memory – Validation Services – integrates with NCICB caCORE components such as Enterprise Vocabulary Service (EVS) and W3C XML schema validation services – Mapping Tool – maps clinical data to the HL7 version 3 message specification currently, with extensible mapping and data transformation in the near future – caAdapter API – uses mappings to generate HL7 version 3 messages – Message Service – integrates with message exchange services (future plans)

37 37 HL7 Version 3 at NCICB: caAdapter  A platform to enable clinical applications to build and parse HL7 v3 messages based on specific schema definitions.  Capability to perform vocabulary validation of the RIM structural attributes.  An open source solution for implementing an international messaging standard allowing data to be exchanged between disparate systems.  Integration with NCI metadata repository (caDSR) and terminology services (EVS)  Facilitating the building and parsing of HL7 v3 messages from source clinical systems will promote data exchange in a standards based common format.

38 38 Recommended Resources Health Level Seven HL7 Reference Information Model https://www.hl7.org/library/data-model/RIM/C30202/rim.htm HL7 Vocabulary Domains HL7 Version 3 Standard NCICB caAdapter Project Site trials.nci.nih.gov/projects/infrastructureProject/caAdapter HL7 Version 3: Driving Interoperability & Transforming Healthcare Information Management - Charles Mead, MD, MSc NIHSeminar_Charlie Mead.ppt


Download ppt "1 HL7 Version 3 at NCICB Overview  Session Details  Introduction  Reference Information Model (RIM)  HL7 Modeling Conventions  HL7 Process & Artifacts,"

Similar presentations


Ads by Google