SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October 2002 - Page: 1 Notification Messaging to Support FDA Building an HL7 Version.

Slides:



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

The Public Health Conceptual Data Model HL7 RIM Harmonization May 2000.
Depicting EHRs Immunization capability HL7 WGM – September 11, 2006 Immunization Storyboard project update.
Quality Improvement/ Quality Assurance Amelia Broussard, PhD, RN, MPH Christopher Gibbs, JD, MPH.
Deepthi Rajeev, MS, MSc Department of Biomedical Informatics University of Utah Evaluating the Impact of Electronic Disease Surveillance Systems On Local.
Overview of OASIS SOA Reference Architecture Foundation (SOA-RAF)
IS550: Software requirements engineering Dr. Azeddine Chikh 4. Validation and management.
Hetty Khan Health Informatics Scientist Centers for Disease Control and Prevention (CDC) National Center for Health Statistics (NCHS) August 7, 2012 Developing.
HL7 UK 2003 (c) Abies Ltd Modelling Clinical Information Using UML Tim Benson Abies Ltd
Development Principles PHIN advances the use of standard vocabularies by working with Standards Development Organizations to ensure that public health.
The Final Standards Rule John D. Halamka MD. Categories of Standards Content Vocabulary Privacy/Security.
Initial slides for Layered Service Architecture
Common Data Elements and Metadata: Their Roles in Integrating Public Health Surveillance and Information Systems Ron Fichtner, Chief, Prevention Informatics.
S New Security Developments in DICOM Lawrence Tarbox, Ph.D Chair, DICOM WG 14 (Security) Siemens Corporate Research.
SWIS Digital Inspections Project (SWIS DIP) Chris Allen, Information Management Branch California Integrated Waste Management Board November 5, 2008 The.
CSSM Meeting Summary Fall 2012 Meetings 15 – 18 October E. Barkley Chair (NASA/JPL) C. Haddow Co-Chair (ESA/ESOC) Cleveland, Ohio, USA.
Integration Project Team Tom Starcher, NCCDPHP Scott Danos, NCHSTP Dan Jernigan, NCID Henry Rolka, NIP Roseanne English, HISSB Exec. Sec. Kim Marsh, HISSB.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Chapter 6 Requirements Engineering Process.
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
HL7 HL7  Health Level Seven (HL7) is a non-profit organization involved in the development of international healthcare.
ONC Standard and Interoperability (S&I) Public Health Reporting Initiative (PHRI) Nikolay Lipskiy, MD, DrPH; CDC ONC S&I PHRI Co-Lead November 8, 2012.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.
Introduction to Sequence Diagrams
IHE Profile – SOA Analysis: In Progress Update Brian McIndoe December 6, 2010.
National Institute of Standards and Technology Technology Administration U.S. Department of Commerce 1 Patient Care Devices Domain Test Effort Integrating.
1 Health Level Seven (HL7) Report Out Population Science and Structured Documents Workgroup (SDWG) Riki Ohira September 22, 2011.
Toolkit for Planning an EHR-based Surveillance Program | HL7 Clinical Document Architecture An Introduction.
Comcare Compliance Assistance Section Presents Incident Notification.
Public Health Vocabulary Services (a) Gautam Kesarinath – CDC NCPHI Associate Director of Technology, (b) Nikolay Lipskiy – CDC SDO & Interoperability.
Public Health Reporting Initiative: Stage 2 Draft Roadmap.
Interoperability Showcase In collaboration with IHE Use Case 3 Care Theme: Leveraging National Healthcare Registries in Care Delivery Biosurveillance Monitoring.
Networking and Health Information Exchange Unit 6b EHR Functional Model Standards.
Understanding the Vital Records Functional Profile (VRFP) Hetty Khan Health Informatics Specialist Centers for Disease Control and Prevention National.
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
DATABASES Southern Region CEO Wednesday 13 th October 2010.
Public Health Reporting Initiative April 4, 2012.
Networking and Health Information Exchange Unit 5b Health Data Interchange Standards.
IHE Profile – SOA Analysis: In Progress Update Brian McIndoe January 18, 2011.
Public Health Data Standards Consortium
Message Development Framework (MDF) Is a Methodology for building HL7 models Is a description for defining HL7 standard messages Full instruction.
Framing the Issue: FDA Perspective Product Tracing Sherri A. McGarry Center for Food Safety and Applied Nutrition Food and Drug Administration.
Health IT Workforce Curriculum Version 1.0 Fall Networking and Health Information Exchange Unit 3b National and International Standards Developing.
Public Health Data Standards Consortium
Public Health Reporting Initiative Stage 3 Sprint: Implementation Guide Development 1.
Health eDecisions Use Case 2: CDS Guidance Service Strawman of Core Concepts Use Case 2 1.
Standards for Technology in Automotive Retail STAR Update Michelle Vidanes STAR XML Data Architect April 30 th, 2008.
Meeting Etiquette Please announce your name each time prior to making comments or suggestions during the call Remember: If you are not speaking keep your.
Issues in Ontology-based Information integration By Zhan Cui, Dean Jones and Paul O’Brien.
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
Commentary: The HL7 Reference Information Model as the Basis for Interoperability George W. Beeler, Jr. Ph.D. Co-Chair, HL7 Modeling & Methodology.
FDA Standards Development and Implementation Randy Levin, M.D. Director, Office of Information Management Center for Drug Evaluation and Research Food.
Agenda for Wed, 10/12/11 4-5pm ET 4:00-4:05 Welcome & Intro, John Stinn 4:05-4:10 Update from ONC, Riki Merrick 4:10-4:35 PH Reporting Standardization.
HL7 Version 3 Veli BICER. Agenda HL7 Problems with Version 2.x HL7 Models Use Case Model Information Model Interaction Model Message Model.
Primary Goal: To support case detection and investigation for the reportable infectious diseases (conditions) using electronic information exchanges between.
1 7 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 7 The Object-Oriented Approach to Requirements.
How Good is Your SDTM Data? Perspectives from JumpStart Mary Doi, M.D., M.S. Office of Computational Science Office of Translational Sciences Center for.
Case Study: HL7 Conformance in VA Imaging Mike Henderson Principal Consultant Eastern Informatics, Inc.
Outline of Current Situation Survey on HIV/AIDS (Proposal) Ms. Keiko Dozono Director for AIDS and Emerging Infectious Disease Control Health and Safety.
Informatics for Scientific Data Bio-informatics and Medical Informatics Week 9 Lecture notes INF 380E: Perspectives on Information.
Center for Surveillance, Epidemiology, and Laboratory Services Division of Health Informatics and Surveillance 1 eSHARE Webinar: Roundtable: Jurisdictions’
1 The information contained in this presentation is based on proposed and working documents. Health Information Exchange Interoperability Minnesota Department.
eHealth Standards and Profiles in Action for Europe and Beyond
Dave Iberson-Hurst CDISC VP Technical Strategy
Clinicaltrials.gov Update
Modelling Clinical Information Using UML
Health Information Exchange Interoperability
Laboratory Result Messaging into the NBS
, editor October 8, 2011 DRAFT-D
MSDI training courses feedback MSDIWG10 March 2019 Busan
Presentation transcript:

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 1 Notification Messaging to Support FDA Building an HL7 Version 3 Based Approach for Disease Notification & Applying it to Drug Reaction Reporting

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 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.

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 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  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

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 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  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

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 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  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

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 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  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

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 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.  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.

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 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.  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.

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 9 The Elements of Messaging Analysis  Use Case Model Statement of Requirements We 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.  Use Case Model Statement of Requirements We 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.

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 10 Messaging Analysis Continued  Interaction Model Messaging Scenarios – This documents needs for communication, as well as the discussion around those needs. Interaction Diagram A record of the interactions to be supported Interaction Grid Documents Trigger events, and message dependencies.  Interaction Model Messaging Scenarios – This documents needs for communication, as well as the discussion around those needs. Interaction Diagram A record of the interactions to be supported Interaction Grid Documents Trigger events, and message dependencies.

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 11 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. 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.

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 12 Notification Messaging Scenarios 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 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

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 13 Interaction Specification

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 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.

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 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.  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.

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 16 R-MIM Part 1  Diagram should contain the V3 Outer wrapper and Controlled Act wrapper.  Content determined by HL7 consistently for all messages.  Diagram should contain the V3 Outer wrapper and Controlled Act wrapper.  Content determined by HL7 consistently for all messages.

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 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.  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.

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 18 Notification Payload V1

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 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.  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.

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 20 Downstream Artifacts  Hierarchical Message Description  XML Schemas  Notification Messaging Documentation  Implementation Guides (Disease Specific)  Database/Message Mapping  Messaging Subsystem  Hierarchical Message Description  XML Schemas  Notification Messaging Documentation  Implementation Guides (Disease Specific)  Database/Message Mapping  Messaging Subsystem

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 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.  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.

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 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  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

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 23 Drug Incident Notification

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 24 E2BM Mapping

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 25 Two Forms of Mapping

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 26 Report Patient & Other Parties

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 27 Case Safety Report Details

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 28 Drug Reaction

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 29 Associated Administration

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 30 Proposed Notification Enhancements  Entity identification Name 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 association Relevant time span associations between parties. [Supports BT Response contacts].  Specimen Specimen source, accession number, specimen details. [Supports BT Response and disease surveillance.]  Entity identification Name 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 association Relevant time span associations between parties. [Supports BT Response contacts].  Specimen Specimen source, accession number, specimen details. [Supports BT Response and disease surveillance.]

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 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 information Descriptive text related to an observation. [Supports Drug incident reporting]  Intervention information Interventions, e.g., vaccinations, related to a case. [Supports BT Response, enhanced surveillance, drug incident reporting]  Materials information Add 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.]  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 information Descriptive text related to an observation. [Supports Drug incident reporting]  Intervention information Interventions, e.g., vaccinations, related to a case. [Supports BT Response, enhanced surveillance, drug incident reporting]  Materials information Add 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.]

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 32 Notification V2 - Today

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 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.  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.

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 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.  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.

SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 35 Any More Questions? Mead Walker healthcare informatics consultant Voice: Fax: