1 / 35

Notification Messaging to Support FDA

Notification Messaging to Support FDA. Building an HL7 Version 3 Based Approach for Disease Notification & Applying it to Drug Reaction Reporting. A Basic Premise for the Discussion.

anakin
Download Presentation

Notification Messaging to Support FDA

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. Notification Messaging to Support FDA Building an HL7 Version 3 Based Approach for Disease Notification & Applying it to Drug Reaction Reporting Drug Reaction Notification 2 October 2002 - Page: 1

  2. A Basic Premise for the Discussion There is a core concept that is something like “Notification”. That concept is sufficiently applicable to a wide range of public health activities, ranging from disease notification to drug reaction reporting, for the work done to support NEDSS to be relevant to FDA’s reporting needs. Drug Reaction Notification 2 October 2002 - Page: 2

  3. Presentation Objectives • A little NEDSS • CDC Messaging Development • Notification message contents as an example of the process • Using Notification Messaging to address FDA requirements • Introduce the E2BM mapping • Review mapping contents • HL7 standardization of Notification Messaging • Proposed next steps Drug Reaction Notification 2 October 2002 - Page: 3

  4. 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 Drug Reaction Notification 2 October 2002 - Page: 4

  5. NEDSS & National Standards • Using • Use 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 • Influencing • 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 Drug Reaction Notification 2 October 2002 - Page: 5

  6. Design 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. • Standardize by forwarding messages within HL7 • Influence HL7 • Suggest RIM changes and vocabulary items • Plan to submit message formats for standardization • Work within the technical architecture developed by NEDSS Drug Reaction Notification 2 October 2002 - Page: 6

  7. Using the MDF - CDC Style • Document messaging requirements • Map relevant data to the RIM. Use data mapping as a source for the R-MIM. (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. Drug Reaction Notification 2 October 2002 - Page: 7

  8. Current CDC Projects • Notification Messaging • Communicate notifiable disease reports from states to CDC. • Core component of the NEDSS Base System. • Vital Statistics • Provide a specification for Birth and Death information. • Also support “verification/certification”. • Antimicrobial Use Reporting • Periodic (monthly) reporting of antibiotics use and organism susceptibility from providers to CDC. Drug Reaction Notification 2 October 2002 - Page: 8

  9. The Elements of Messaging Analysis • Use Case Model • Statement of RequirementsWe did not do formal use case analysis. This would be important for a “new” area. • To a certain extent, documentation for the NEDSS Base System addresses this requirement. Drug Reaction Notification 2 October 2002 - Page: 9

  10. Messaging Analysis Continued • Interaction Model • Messaging Scenarios –This documents needs for communication, as well as the discussion around those needs. • Interaction DiagramA record of the interactions to be supported • Interaction GridDocuments Trigger events, and message dependencies. Drug Reaction Notification 2 October 2002 - Page: 10

  11. Notification Messaging Scenarios • Condition NotificationState 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. • Change/Retraction of Prior NotificationState 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. Drug Reaction Notification 2 October 2002 - Page: 11

  12. Notification Messaging Scenarios • Summary NotificationState 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. • Notification ResponseCDC 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 Drug Reaction Notification 2 October 2002 - Page: 12

  13. Interaction Specification Drug Reaction Notification 2 October 2002 - Page: 13

  14. Diagram Based Mapping • Used to discover detailed data requirements. • Can be constructed in a group session. • Becomes an education on the HL7 RIM. • Leads naturally into RMIM construction. • This is the stage we have reached with the FDA specifications. Drug Reaction Notification 2 October 2002 - Page: 14

  15. R-MIM for Notification • Message header to carry transactional information • Identification of the notification sender and receiver • Case specific information • Other notifications related to the case • Patient encounters associated with the case • Case participants including the patient or subject of the case and locations associated with the case. • Associations between participants in the case • Case related specimens and specimen collection procedures. • Observation information, such as laboratory tests, about participants or specimens related to the case. Drug Reaction Notification 2 October 2002 - Page: 15

  16. R-MIM Part 1 • Diagram should contain the V3 Outer wrapper and Controlled Act wrapper. • Content determined by HL7 consistently for all messages. Drug Reaction Notification 2 October 2002 - Page: 16

  17. A Few Comments • This section of the message will change for consistency with new HL7 developments • HL7 will offer a single structure • “Outer Wrapper”: Captures the message header & message sender and receiver. This is basic transactional information. • “Message Control Act”: A single way to model data for the “trigger event”, the event that causes data to flow. Drug Reaction Notification 2 October 2002 - Page: 17

  18. Notification Payload V1 Drug Reaction Notification 2 October 2002 - Page: 18

  19. Comments on the “Payload” • The original design was based on the current NETSS system. • It only reluctantly added data concepts that were not supported there. • Glaring deficiencies are already clear. • Insufficient data for persons • Only observations are linked to the case • Does not address materials, e.g., vaccines. • Insufficient information on specimens. Drug Reaction Notification 2 October 2002 - Page: 19

  20. Downstream Artifacts • Hierarchical Message Description • XML Schemas • Notification Messaging Documentation • Implementation Guides (Disease Specific) • Database/Message Mapping • Messaging Subsystem Drug Reaction Notification 2 October 2002 - Page: 20

  21. Working on FDA Messaging • Initial Premise – We can use the Notification Messages. • Note, this will require enhancement to what is there today. • First Step – Review the E2BM specifications, and recast in HL7 terms. • This was done by mapping the data to the RIM. • Second Step – Determine additional requirements for the Notification Message specification. • I have an initial cut at these. Drug Reaction Notification 2 October 2002 - Page: 21

  22. Produced so Far • High level outline of the E2BM transaction. • Diagrammatic mapping of the specification. • Excel spreadsheet containing the mapping details. • List of proposed updates to the Notification R-MIM Drug Reaction Notification 2 October 2002 - Page: 22

  23. Drug Incident Notification Drug Reaction Notification 2 October 2002 - Page: 23

  24. E2BM Mapping Drug Reaction Notification 2 October 2002 - Page: 24

  25. Two Forms of Mapping Drug Reaction Notification 2 October 2002 - Page: 25

  26. Report Patient & Other Parties Drug Reaction Notification 2 October 2002 - Page: 26

  27. Case Safety Report Details Drug Reaction Notification 2 October 2002 - Page: 27

  28. Drug Reaction Drug Reaction Notification 2 October 2002 - Page: 28

  29. Associated Administration Drug Reaction Notification 2 October 2002 - Page: 29

  30. Proposed Notification Enhancements • Entity identificationName and multiple identifiers for persons, organizations, and locations. Addresses and phone numbers also. [Supports: drug reaction responses, vaccinations. BT Response contacts.] • Material Information about products – materials – that are used in patient treatment, and in clinical trials. [Supports drug reporting, clinical trials.] • Entity associationRelevant time span associations between parties. [Supports BT Response contacts]. • SpecimenSpecimen source, accession number, specimen details. [Supports BT Response and disease surveillance.] Drug Reaction Notification 2 October 2002 - Page: 30

  31. More Notification Enhancements • Location context for environmental specimens.Detailed information describing the place where specimens were collected. Includes detailed location information, and managing the association between locations. [Supports BT Response investigations] • Observation informationDescriptive text related to an observation. [Supports Drug incident reporting] • Intervention informationInterventions, e.g., vaccinations, related to a case. [Supports BT Response, enhanced surveillance, drug incident reporting] • Materials informationAdd materials, in particular drugs and vaccines, to the list of entity types that can be related to a case, and to the acts associated with a case. [Supports vaccine preventable disease surveillance, drug reaction reporting.] Drug Reaction Notification 2 October 2002 - Page: 31

  32. Notification V2 - Today Drug Reaction Notification 2 October 2002 - Page: 32

  33. Later: HL7 Specification Process • Start discussions in HL7. • Pick the time to move forward with a proposal. • Work out whether a new message format is needed – I think it will be. • Address Committee Issues. • Frame a concrete proposal. Drug Reaction Notification 2 October 2002 - Page: 33

  34. Next Steps for Us • Verify the detailed mapping • This has been done • Move forward with a standard message • Create an enhanced Notification Message • Prepare a proposal for HL7 discussion • Carry out education within HL7 • Start process within FDA to lay out the steps leading towards message implementation. Drug Reaction Notification 2 October 2002 - Page: 34

  35. Any More Questions? Mead Walkerhealthcare informatics consultant Voice: 610-518-6259 Fax: 509-357-7983 Email: mead@voicenet.com Drug Reaction Notification 2 October 2002 - Page: 35

More Related