1 / 44

HL7 Publications The Publication Process

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. Overview.

elsu
Download Presentation

HL7 Publications The Publication Process

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. HL7 PublicationsThe 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

  2. 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?

  3. 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

  4. 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.

  5. Section, Sub-Section & Domain Codes

  6. Section, Sub-Section & Domain Codes

  7. Artifact & Document Codes

  8. Legend • 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. 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. ] Sample Committee Naming SchemeSubmitted by: Michael Van Campen, HL7 Canada RIM HL7 e-Claims DIM [ RM00000 ] Superset of all RMIMs etc. Superset of all HMDs E01 RMIM [ RM01000 ] E02 RMIM [ RM02000 ] etc. Generic HMD[ HD01000 ] Pharmacy HMD[ HD01100 ] Laboratory HMD[ HD01200 ] Generic Laboratory MT [ MT01200] Generic Pharmacy MT [ MT01100] Generic MT [ MT01000] Payor1 MT [ MT01001 ] Payor2 MT [ MT01002 ] Payor1 MT [ MT01101 ] Payor2 MT [ MT01102 ] Payor1 MT [ MT01201 ] Payor2 MT [ MT01202 ] etc. etc. etc.

  9. 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?

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

  11. 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

  12. Domain introduction Application Roles

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

  14. General Orders Status Change RMIM

  15. 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

  16. Storyboard Interaction Diagram

  17. 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

  18. Repository Screenshot (Rosetree) HMD Common HMD Message Types

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

  20. 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.

  21. 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 DatabaseSSUU_DD_PBnnnnn.mdb • Narrative DocumentsSSUU_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.

  22. 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?

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

  24. 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.

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

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

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

  28. Visio files GIF files Visio files GIF files Visio files GIF files Visio files GIF files Visio files GIF files 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 Save-As Crop

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

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

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

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

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

  34. 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?

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

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

  37. V3 Backbone • Introduction • Principles • Managing message development • Quick Start • Getting Started • Glossary • 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

  38. HL7 V3 Guide • Instruction manual for understanding the V3 Ballot and Specification • Overview and Metamodel • Storyboards • Information Model • Vocabulary • Interaction Model • Conformance • Message Specification • Replaces Message Development Framework in publication. • Focus on the ballot publication, not development methodology. HL7 V3 Guide

  39. 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 Health & Clinical Management Section Administrative Management Section Infrastructure Management

  40. 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

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

  42. 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!

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

  44. Questions ?

More Related