Presentation is loading. Please wait.

Presentation is loading. Please wait.

CDC Message Development Using HL7 Version 3 Principles Mead Walker January 8, 2002.

Similar presentations


Presentation on theme: "CDC Message Development Using HL7 Version 3 Principles Mead Walker January 8, 2002."— Presentation transcript:

1 CDC Message Development Using HL7 Version 3 Principles Mead Walker January 8, 2002

2 Presentation Outline Introduce CDC Projects Using national standards HL7 in particular Review progress so far Consider impacts on V3 development What about impacts on other government work?

3 2002-01-083CDC Version 3 Messaging Messaging Projects Notification managing notificable disease reports Vital Statistics Birth and Death information Anti-Microbial Resistance Reporting on antibiotic susceptibility and pharmacy drug use The context for these projects is provided by something called NEDSS

4 2002-01-084CDC Version 3 Messaging A Vision for National Electronic Disease Surveillance System (NEDSS) Gathers health data automatically from a variety of sources on a real-time basis Monitors the health of communities Assists in ongoing analyses of trends and detection of emerging public health problems Provides information for setting public health policies Is a system of interoperable systems like the Internet is a network of interoperable networks – is not a software program

5 2002-01-085CDC Version 3 Messaging NEDSS at-a-glance NEDSS is a broad initiative using national data and information system standards for development of efficient, integrated, and interoperable surveillance systems at the state and local levels –Data standardsConceptual data model, http://www.cdc.gov/cic http://www.cdc.gov/cic –Harmonizing with HL7 Reference Information Model –NEDSS System Architecture http://www.cdc.gov/cic Includes tools for electronic data transfer to health department from health care system: –Eg from multi-jurisdictional clinical labs Architecture built on Integrated Data Repository; data from health care to health department sent via –single pipeline: single format, receiving point, security Security standards (HIPAA compliant) to maintain public health track record in protecting sensitive data Starts with focusinfectious diseasebut keeps big picture in mind

6 2002-01-086CDC Version 3 Messaging Standards and Derived Specifications National Standards true standards needed for sharing conceptual not specific enough Design Specifications standards? physical risk of proprietary nature need national underpinning

7 2002-01-087CDC Version 3 Messaging Standards and Derived Specifications National Standards true standards needed for sharing conceptual not specific enough Design Specifications standards? physical risk of proprietary nature need national underpinning Use national standards wherever possible Use and publish design specifications in order to do the work Have a very high bar to change vs. derive Be prepared to follow the refinement of standards

8 2002-01-088CDC Version 3 Messaging Standards and Derived Specifications National Standards true standards needed for sharing conceptual not specific enough Design Specifications standards? physical risk of proprietary nature need national underpinning See that public health issues are represented in national standards Document specification development activities Use opportunities to promote the sometimes more difficult approach of using standards

9 2002-01-089CDC Version 3 Messaging A Philosophy for CDC Messaging Projects Develop HL7 Version 3 messages. –Use the RIM and the Message Development Framework. –Use HL7 vocabulary domains –Create a consistent set of work products across the projects. Influence HL7 –Suggest RIM changes and vocabulary items –Plan to submit message formats for standardization Work within the technical architecture developed by NEDSS

10 2002-01-0810CDC Version 3 Messaging Using the MDF - CDC Style Document messaging requirements Map relevant data to the RIM. Use data mapping as a source for the RMIM. (These two can be documented together with simple source data.) HL7 tooling supports definition of HMDs, message types, and XML schemas. Create mappings between message elements and source and target databases Address vocabulary issues by looking at HL7 domains first, but not last.

11 2002-01-0811CDC Version 3 Messaging Current CDC Projects Notification Messaging –Communicate notifiable disease reports from states to CDC. –This is a core component of the NEDSS Base System. Vital Statistics –Provide a specification for Birth and Death information. –There is also a need to support verification/certification. Antimicrobial Use Reporting –Periodic (monthly) reporting of antibiotics use and organism susceptibility from providers to CDC. –This is expected to be expanded to support reporting on individual isolates.

12 2002-01-0812CDC Version 3 Messaging Messaging Analysis Statement of Requirements We did not do formal use case analysis. This would be important for a new area. Messaging Scenarios This documents needs for communication, and the discussion around those needs. Interaction Diagram A record of the interactions to be supported Interaction Grid Documents Trigger events, and message dependencies.

13 2002-01-0813CDC Version 3 Messaging Notification Messaging Scenarios I.Condition Notification State or other reporting base system sends a notification to CDC. CDC will acknowledge receipt. A negative acknowledgement will be sent if the message that has been received cannot be processed. II.Change/Retraction of Prior Notification State or other reporting base system sends a notification update/change/retraction. This message will always provide a reference to the earlier notification that is being updated, changed, or retracted. CDC will acknowledge receipt. A negative acknowledgement will be sent if the message that has been received cannot be processed. III.Summary Notification State or other reporting base system provides total amounts for the reporting, during a specified time period, of a specific disease or condition to CDC. CDC will acknowledge receipt. A negative acknowledgement will be sent if the message that has been received cannot be processed. IV.Notification Response CDC will provide a response to the state or other reporting base system once the CDC base system has processed the message. This message will indicate that the message was successfully processed by the interface engine. The state or other reporting base system will acknowledge receipt. A negative acknowledgement will be sent if the message that has been received cannot be processed

14 2002-01-0814CDC Version 3 Messaging Interaction Specification

15 2002-01-0815CDC Version 3 Messaging Diagram Based Mapping Can be constructed in a group session. Becomes an education on the HL7 RIM. Leads naturally into RMIM construction.

16 2002-01-0816CDC Version 3 Messaging Mapping from Source Data The detailed tabular mapping: –Covers a wealth of data –Includes domain information –Allows room for comments.

17 2002-01-0817CDC Version 3 Messaging Notification RMIM (Rose UML model)

18 2002-01-0818CDC Version 3 Messaging Message Artifacts: HMD Fragment

19 2002-01-0819CDC Version 3 Messaging Message Artifacts II: Schema Fragment Notification Report NEDSSNTF_V1_001 NTF_V1_001.01 NND 00.16.01 Class N Message_interaction MI_Notification NEDSSNTF_V1_001-NEDSSNTF_V1_001-MI_Notfctn-hmd Notification Report NEDSSNTF_V1_001 NTF_V1_001.01 NND 00.16.01 Class N Message_interaction MI_Notification NEDSSNTF_V1_001-NEDSSNTF_V1_001-MI_Notfctn- hmd

20 2002-01-0820CDC Version 3 Messaging Lessons Learned and to be Worked on The process for creating message specifications works XML has wide credibility, and becomes a major selling point. However XML implementation skills are just developing. (Specifically the implementation of XML as a messaging format.) The tooling to support schema creation is still evolving. HL7 datatypes can provide a shock. This needs to be cushioned by agreed on methods for simplification.

21 2002-01-0821CDC Version 3 Messaging Item for Discussion What about impacts on other government work?

22 Any More Questions? Mead Walker Health Data & Interoperability Consulting T: 610-518-6259 F: 509-357-7983 E: mead@voicenet.com


Download ppt "CDC Message Development Using HL7 Version 3 Principles Mead Walker January 8, 2002."

Similar presentations


Ads by Google