2. HL7 Publications The Publication Process Helen Stevens Senior Project Manager – Architecture McKesson Information Solutions HL7 Publications Committee Chair HL7 Canada Implementation Committee Chair HL7 Orders/Observations Committee Co-Chair

3. Overview  Artifacts, Contents and Naming Conventions What are the parts of the HL7 ballot and their naming conventions?  HL7 technical committee input What are the forms of content submission from the HL7 technical committees?  Publication Process What is the process used to convert the committee submissions into the publication?  Publication product What is the product of V3 Publication?

4. Why a naming convention?  Artifacts are uniquely identified Avoids conflicts/duplicates between committees or working groups  Artifact types and responsibilities are clearly defined and understood from the name Increases accuracy and efficiency in ensuring that correct artifacts are published properly  High volume of artifacts and submissions being received from many committees to be coordinated centrally by publications

5. Sections Health & Clinical  Management of the health and clinical care of individuals. Includes Orders/Observations, Reasoning (Patient Care/Decision Support) and Medical Records Administrative  Administrative management of health care enterprises, assuming a separation of duties that distinguishes between the provision of health and clinical services and the management of the processes whereby those services are provided. Infrastructure  Information structures and communications tools to support the interactions specified by the Health & Clinical and Administrative Sections.  Focus on the logical structures used to convey clinical and administrative information rather than on the clinical or administrative information itself. Section Administrative Management Section Health & Clinical Management Section Infrastructure Management

6. Artifact Naming All artifacts delivered for V3 must be named using the following convention: SSUU_DD_AAnnnnn SS = Section code UU = Sub-Section code DD = Domain code AA = Artifact or Document code nnnnn = Five digit zero-filled number assigned by Domain. Domain may assign this number in any way they wish to organize their artifacts. Example: HMPO_RX_AR00001 Health & Clinical Section, Practices & Operations Sub- Section, Pharmacy Domain, Application Role Artifact number 00001.

7. Section, Sub-Section & Domain Codes HM Section: Health & Clinical Management POSub-Section: Practice & Operations LBDomain: Laboratory RXDomain: Pharmacy RESub-Section: Reasoning PCDomain: Patient Care RCSub-Section: Records MRDomain: Medical Records AMSection: Administrative Management PRSub-Section: Practice PADomain: Patient Administration SCDomain: Scheduling FISub-Section: Financial FMDomain: Financial Management CRDomain: Claims & Reimbursement ABDomain: Accounting & Billing IMSection: Infrastructure Management COSub-Section: Control MCDomain: Message Control MFDomain: Master File Update QUSub-Section: Query QDDomain: Query Applicable to all sub-sections XXNon Domain Specific CMCMET

8. Section, Sub-Section & Domain Codes

9. Artifact & Document Codes

10. Sample Committee Naming Scheme Submitted by: Michael Van Campen, HL7 Canada RIM e-Claims DIM [ RM00000 ] E01 RMIM [ RM01000 ] E02 RMIM [ RM02000 ] Generic HMD [ HD01000 ] RMIM: Digits 1,2 [ 00 = Super RMIM 01 = E01 02 = E02 etc. ] HMD: Digit 3 [ 0 = Generic 1 = Pharmacy 2 = Laboratory etc. ] MT: Digits 4,5 [ 00 = Generic 01 = Payor1 02 = Payor2 etc. ] HL7 Payor2 MT [ MT01202 ] etc. Superset of all HMDs Superset of all RMIMs Pharmacy HMD [ HD01100 ] Laboratory HMD [ HD01200 ] RIM- Reference Information Model DIM (RM)- Domain Information Model RMIM (RM)- Refined Message Info Model HMD (HD)- Hierarchical Message Defn. MT (MT)- Message Type (message) Naming convention: AARRHMM, where AA is the artifact code (RM, HD, MT), RR is the RMIM id, H is the HMD id, MM is the MT id. Legend Payor1 MT [ MT01201 ] Generic Laboratory MT [ MT01200] Payor2 MT [ MT01002 ] etc. Payor1 MT [ MT01001 ] Generic MT [ MT01000] Payor2 MT [ MT01102 ] etc. Payor1 MT [ MT01101 ] Generic Pharmacy MT [ MT01100]

11. Overview  Artifacts, Contents and Naming Conventions What are the parts of the HL7 ballot and their naming conventions?  HL7 technical committee input What are the forms of content submission from the HL7 technical committees?  Publication Process What is the process used to convert the committee submissions into the publication?  Publication product What is the product of V3 Publication?

12. Committee Deliverables 1.Domain Database Application Roles Interaction Categories  Storyboards & Examples  Trigger Events  Interactions R-MIM, HMD and Message Type Descriptions 2.Diagrams Refined Message Information Models (R-MIM) Storyboard Interaction Diagrams Other Diagrams 3.Design Repository R-MIM Hierarchical Message Descriptors (HMD) Message Types 4.XML Narrative Introductions

13. Domain Database  MS Access database developed by Austin Kriesler (McKesson) for HL7 to help the technical committees to manage 3.0 artifacts and documentation  One database for each publication domain  Contains all content except for extended narratives, diagrams and Rose Tree generated messages

14. Domain introduction Application Roles

15. Interaction Categories Trigger Events

16. Interactions Storyboards

17. R-MIM & HMD Descriptions

18. RMIM Diagrams  VISIO diagrams generated using HL7 Stencil developed by Lloyd McKenzie (HL7 Canada) to document RMIM designs  One diagram for each RMIM developed

19. General Orders Status Change RMIM

20. Other Diagrams  Storyboard interaction diagrams are required to support each storyboard submitted  Other diagrams may also be developed to support narrative content or provide additional value to the content.   Recommend use of VISIO to build and maintain all diagrams

21. Storyboard Interaction Diagram

22. Repository Database  MS Access database developed by Woody Beeler (Beeler Consulting) to store message designs including RIM, RMIM, HMD, and Message Types that are generated by Rosetree  One or more databases for each domain

23. Repository Screenshot (Rosetree) HMDCommon HMDMessage Types

24. Converting VISIO to Repository  Using HL7 menu in VISIO R-MIM diagrams can be automatically verified against current RIM and converted into Rosetree Repository

25. XML Narratives  Narratives maintained and submitted in XML for Sub-Section or Domain introductions. Publications committee will perform initial conversion from Word to XML, but document must be maintained in XML unless specific arrangement made with publications.  Required when introductions includes diagrams, tables or formatted text that cannot be entered into the Domain Database directly.

26. TC Submissions Submissions from TCs for V3 must be in files named as follows: Repository Database SSUU_DD_RPnnnnn.mdb RMIM Diagram(s) SSUU_DD_RMnnnnn.vsd (one diagram per file) Storyboard Diagram(s) SSUU_DD_STnnnnn.vsd (one diagram per file) Publication/ Domain Database SSUU_DD_PBnnnnn.mdb Narrative Documents SSUU_DD_NAnnnnn.mdb Submit Files to http: //www.hl7.org/v3 If an update to a file must be submitted, then it should be named exactly the same as the original file. HQ will automatically add a timestamp to received files and keep all historical files.

27. Overview  Artifacts, Contents and Naming Conventions What are the parts of the HL7 ballot and their naming conventions?  HL7 technical committee input What are the forms of content submission from the HL7 technical committees?  Publication Process What is the process used to convert the committee submissions into the publication?  Publication product What is the product of V3 Publication?

28. Publication Format Publication in two final formats: 1.PDF appropriate for printing, submission to ANSII and off-line viewing Each document available as ‘stand alone’ or will be inter-linked * 2.HTML Appropriate for viewing online Each document can be downloaded separately * * Backbone is required

29. Using XML  All documentation will be converted from XML into PDF and HTML  Primary ‘source of truth’ for normative content is the HL7 Repository.  HL7 Repository is Microsoft Access database.

30. Publication Process 1.Build the Master Repository Database 2.Build the Master Domain Database  Note: currently publication uses two master databases, in future this may be merged to be the same database. 3.Convert Diagrams 4.Generate Publication from Databases  Section content (Repository + Domain Db)  Reference Information Model  Vocabulary 5.Generate other publication documents

31. Visio files Master Repository (DMIM/RMIM/HMD/MT) Repository Database Build Master Repository Post Merge repositories Migrate repositories 3 1. 1.Verify VISIO diagrams against repository database contents 2. 2.Verify repository database is self- consistent (names, duplicates etc.) 3. 3.Merge repositories and migrate to Master repository containing RIM & Vocabulary 2 Verify 1

32. Build Master Domain Visio files Master Domain Db Post RepLinker Importer 3 1. 1.Verify VISIO & other diagrams against domain database contents 2. 2.Verify domain database is self- consistent (names, duplicates etc.) 3. 3.Use RepLinker to import domain databases into blank Master DomainDb 2 Verify Domain Database 1 Verify

33. Convert Diagrams  HL7 publishes using GIF format diagrams  All diagrams are saved-as GIF from VISIO (or any other submitted format) and cropped appropriately  This is currently a manual process Visio files Save-As GIF files Crop

34. HTML Files Formatting Objects(fo) XML File XML Document Transform Master Repository (DMIM/RMIM/HMD/MT) XML Extract DTD Base HTML XSL Document Specific HTML XSL PDF Files Transform Document Specific fo (PDF) XSL Base fo (PDF) XSL Render XEP* Program *RenderX Corp. Generating HTML and PDF

35. Master Repository – RMIM/HMD/MT Generating HTML and PDF Master Repository - RIM HTML Files Formatting Objects(fo) XML File XML Document Transform XML Extract DTD Base HTML XSL Document Specific HTML XSL PDF Files Transform Document Specific fo (PDF) XSL Base fo (PDF) XSL Render XEP* Program *RenderX Corp.

36. Master Repository – RMIM/HMD/MT Generating HTML and PDF Master Repository - RIMMaster Repository - Vocabulary HTML Files Formatting Objects(fo) XML File XML Document Transform XML Extract DTD Base HTML XSL Document Specific HTML XSL PDF Files Transform Document Specific fo (PDF) XSL Base fo (PDF) XSL Render XEP* Program *RenderX Corp.

37. Master Repository – RMIM/HMD/MT Generating HTML and PDF Master Repository - RIMMaster Repository - VocabularyMaster Domain Database HTML Files Formatting Objects(fo) XML File XML Document Transform XML Extract DTD Base HTML XSL Document Specific HTML XSL PDF Files Transform Document Specific fo (PDF) XSL Base fo (PDF) XSL Render XEP* Program *RenderX Corp. XML Narratives

38. HTML Files Formatting Objects(fo) XML File XML Document Transform XML Extract DTD Base HTML XSL Document Specific HTML XSL PDF Files Transform Document Specific fo (PDF) XSL Base fo (PDF) XSL Render XEP* Program *RenderX Corp. Master Repository – RMIM/HMD/MT Generating HTML and PDF Master Repository - RIMMaster Repository - VocabularyMaster Domain Database XML Documents Data Types 1 and 2 XML Implementation Technology Spec V3 Publication Backbone V3 Guide

39. Overview  Artifacts, Contents and Naming Conventions What are the parts of the HL7 ballot and their naming conventions?  HL7 technical committee input What are the forms of content submission from the HL7 technical committees?  Publication Process What is the process used to convert the committee submissions into the publication?  Publication product What is the product of V3 Publication?

40. HL7 3.0 Core Publication Structure V3 Backbone Welcome Introduction V3 Principles Quick Start Getting Started Glossary V3 Guide Implementable Technology Specifications XML Data Types Part I Part II Sub-sections Section Infrastructure Management Sub-sections Section Administrative Management Sub-sections Section Health & Clinical Management Normative: Content is balloted by general membership and is considered structural component of HL7 standard. Negative ballots MUST be resolved. Reference: Content is harmonized during HL7 meetings or approved by the HL7 Board. It is not subject to ballot acceptance Informative: Content is balloted by general membership; however, it is not considered to be a structural part of the standard, only supporting information. Vocabulary Normative Reference Informative Legend: Reference Information Model State Machines Literary Expression RIM Diagram

41. HL7 3.0 Section Publication Structure Sub-sections Domain CMET Storyboard Application Roles Interaction Category R-MIM HMD Message Type Interaction Trigger Event R-MIMHMD Storyboard Examples Message Type Normative Reference Informative Legend:

42. V3 Backbone 1.Introduction 2.Principles 3.Managing message development 4.Quick Start 5.Getting Started 6.Glossary 7.Links to all other documents & content. Differing ‘entry points’ for different users: New Implementer Project Manager / Manager / Marketer Interface Developer / Analyst / Programmer Standards Developer V3 Backbone Welcome Introduction Quick Start Getting Started Glossary

43. HL7 V3 Guide  Instruction manual for understanding the V3 Ballot and Specification 1.Overview and Metamodel 2.Storyboards 3.Information Model 4.Vocabulary 5.Interaction Model 6.Conformance 7.Message Specification  Replaces Message Development Framework in publication.  Focus on the ballot publication, not development methodology. HL7 V3 Guide

44. Sections Health & Clinical  Management of the health and clinical care of individuals. Includes Orders/Observations, Reasoning (Patient Care/Decision Support) and Medical Records Administrative  Administrative management of health care enterprises, assuming a separation of duties that distinguishes between the provision of health and clinical services and the management of the processes whereby those services are provided. Infrastructure  Information structures and communications tools to support the interactions specified by the Health & Clinical and Administrative Sections.  Focus on the logical structures used to convey clinical and administrative information rather than on the clinical or administrative information itself. Section Administrative Management Section Health & Clinical Management Section Infrastructure Management

45. Final HTML Presentation   New HL7 ‘look & feel’ using green/blue colour scheme   Pull down menus for quick navigation   Specific help documentation and access to discussion boards to support membership reviews

46. E-Claims Demonstration Michael van Campen E-claims TAG Chair Technical Architecture Group HL7 PAFM TC Co-chair (acting) Responsible for Financial Management

47. Next Release Plans  Improved download/distribution system  Improved faster menus  Improved graphic presentation  Improved HMD & Message Type presentation  PDF for Vocabulary and HMD  Examples  Increased hyper linking  On-line help files  Possibly on-line automated balloting tool  More… feedback and contributions welcome!

48. Salt Lake October 2001 San Diego January 2002 Atlanta April 2002 Baltimore September 2002 Anticipated Schedule Committee Ballot #1 Review Committee Ballot # 1 V3.0 Release Membership Ballot Review Membership Ballot Committee Ballot #2 Review Committee Ballot #2 Ballot 2 Development

49. Questions ?