Lab Public Health Reporting Content: Difference between revisions
| Line 32: | Line 32: | ||
''NOTE: we are working with HITSP/PHDSC to refine this use case'' | ''NOTE: we are working with HITSP/PHDSC to refine this use case'' | ||
John Doe, MD sees a patient and suspects that this patient has an enteric pathogen. The patient follows through on the doctor’s orders and submits a specimen to the clinic | John Doe, MD sees a patient and suspects that this patient has an enteric pathogen. The patient follows through on the doctor’s orders and submits a specimen to the clinic laboratory. Upon completion of laboratory analysis, the laboratory confirms the presence of Salmonella. When a microbiologist has time in the week, they gather all their reportable results and complete the forms for submission to the state public health agency. Additionally, the clinic laboratory needs to submit the Salmonella specimen to the public health laboratory for serotyping. This specimen is mailed along with a hand written requisition to the state laboratory for epidemiological serotyping. | ||
Additionally, the clinic laboratory | |||
The state laboratory identifies | The state laboratory enters the partial information written on the requisition and identifies the Salmonella serotype. A nightly batch process reports the serotype to the clinician. A monthly batch process generates a file for the CDC. Nearby states have small clusters of cases with this same Salmonella serotype. No outbreak investigation is initiated. | ||
The | The CDC detects this anomaly as monthly reports are received when observed across state borders and an outbreak protocol is started to investigate the potential outbreak. The CDC requests PFGE on the known samples and the outbreak is quickly confirmed two months later. Calls, faxes, and emails are used to transmit information to relevant state, county, local programs, and submitters of outbreak samples. Significant efforts on resolution focus on getting the desired data to the necessary participants. The outbreak is investigated and linked to a restaurant supplier in a popular but off-season resort area. | ||
After this profile is adopted: | '''After this profile is adopted:''' | ||
The | |||
The clinical laboratory creates a laboratory report identifying the organism as a Salmonella isolate and that further serotyping will be done at the State Lab. The laboratory report is sent to the clinician, stored within the patient’s electronic medical record, and registered in a clinical interoperability registry. The isolate is mailed to the public health lab. | |||
Upon arrival, the public health laboratory receiving department queries the clinical interoperability registry with the submitter’s patient ID and views the initial laboratory report. The public health laboratory information system pulls forward the patient’s demographic and specimen data from the initial laboratory report. The public health laboratory creates a new laboratory report identifying the Salmonella serotype. The laboratory report is sent to the clinician, stored within the patient’s electronic medical record, registered in the clinical interoperability registry, registered in the state public health interoperability registry, and registered in the national public health interoperability registry. | |||
The CDC program monitors the national public health registry for new cases of Salmonella. An anomaly is immediately detected in the number of new cases for this particular Salmonella serotype when observed across state borders and an outbreak protocol is started immediately to investigate the potential outbreak. The CDC requests PFGE on the current samples and alerts all state laboratories to perform PFGE on new samples of this serotype. The outbreak is confirmed quickly and new cases are identified and tracked seamlessly. | |||
Local, state, and federal epidemiologists and case workers have access to all laboratory reports within their respective interoperability registries and may potentially gain further access to the clinical interoperability registry for additional information, such as the ordering provider and care location, for initiating further investigation. | |||
'''Key improvements include:''' | |||
* avoid handwritten forms and data re-entry | |||
* ease transition of data to and from clinical care and public health agencies | |||
* ease transition of data from one public health agency to another | |||
* monitor registries for anomalies in a real-time basis | |||
* response protocols focus on response, not the access to data | |||
===Actors/Transaction=== | ===Actors/Transaction=== | ||
Revision as of 19:40, 28 March 2007
Introduction
This is a draft of the Lab Public Health Reporting Content Profile supplement to the Patient Care Coordination Technical Framework. This draft is a work in progress, not the official supplement or profile.
Motivation
The motivation for developing this profile is as follows:
- Show that the same standards that support the current IHE profiles for clinical care interoperability can be leveraged by population health.
- Encourage the public health community to come forward to IHE with use cases to further enhance data sharing.
Profile Abstract
NOTE: we are working with HITSP/PHDSC to refine this definition
Our goal with this profile is to adapt XDS-LAB integration content profile to accommodate data for a public health laboratory report. Modifications to XDS-LAB will be needed to accommodate non-human subjects, document participants in the laboratory testing process, and to group tests for a reportable condition in a consistent manner. Leveraging the CDA R2 standard and the XDS-LAB profile make the resultant document not only consumable by public health, but able to be sent back to the clinical care provider and even possible to include into an effected patient’s medical record thereby completing a communication loop between individual and population care.
Glossary
- no terms, yet
Volume I
Introduction
Profile Dependencies
- XD*
- XDS-Lab
Profile Name
The Lab Public Health Reporting integration content profile adapts XDS-Lab to accommodate data for a public health laboratory report. Modifications to XDS-LAB will be needed to accommodate non-human subjects, document participants in the laboratory testing process, and to group tests for a reportable condition in a consistent manner. Leveraging the CDA R2 standard and the XDS-LAB profile make the resultant document not only consumable by public health, but able to be sent back to the clinical care provider and even possible to include into an effected patient’s medical record there upon effectively closing the communication loop between individual and population care.
Use Cases
NOTE: we are working with HITSP/PHDSC to refine this use case
John Doe, MD sees a patient and suspects that this patient has an enteric pathogen. The patient follows through on the doctor’s orders and submits a specimen to the clinic laboratory. Upon completion of laboratory analysis, the laboratory confirms the presence of Salmonella. When a microbiologist has time in the week, they gather all their reportable results and complete the forms for submission to the state public health agency. Additionally, the clinic laboratory needs to submit the Salmonella specimen to the public health laboratory for serotyping. This specimen is mailed along with a hand written requisition to the state laboratory for epidemiological serotyping.
The state laboratory enters the partial information written on the requisition and identifies the Salmonella serotype. A nightly batch process reports the serotype to the clinician. A monthly batch process generates a file for the CDC. Nearby states have small clusters of cases with this same Salmonella serotype. No outbreak investigation is initiated.
The CDC detects this anomaly as monthly reports are received when observed across state borders and an outbreak protocol is started to investigate the potential outbreak. The CDC requests PFGE on the known samples and the outbreak is quickly confirmed two months later. Calls, faxes, and emails are used to transmit information to relevant state, county, local programs, and submitters of outbreak samples. Significant efforts on resolution focus on getting the desired data to the necessary participants. The outbreak is investigated and linked to a restaurant supplier in a popular but off-season resort area.
After this profile is adopted:
The clinical laboratory creates a laboratory report identifying the organism as a Salmonella isolate and that further serotyping will be done at the State Lab. The laboratory report is sent to the clinician, stored within the patient’s electronic medical record, and registered in a clinical interoperability registry. The isolate is mailed to the public health lab.
Upon arrival, the public health laboratory receiving department queries the clinical interoperability registry with the submitter’s patient ID and views the initial laboratory report. The public health laboratory information system pulls forward the patient’s demographic and specimen data from the initial laboratory report. The public health laboratory creates a new laboratory report identifying the Salmonella serotype. The laboratory report is sent to the clinician, stored within the patient’s electronic medical record, registered in the clinical interoperability registry, registered in the state public health interoperability registry, and registered in the national public health interoperability registry.
The CDC program monitors the national public health registry for new cases of Salmonella. An anomaly is immediately detected in the number of new cases for this particular Salmonella serotype when observed across state borders and an outbreak protocol is started immediately to investigate the potential outbreak. The CDC requests PFGE on the current samples and alerts all state laboratories to perform PFGE on new samples of this serotype. The outbreak is confirmed quickly and new cases are identified and tracked seamlessly.
Local, state, and federal epidemiologists and case workers have access to all laboratory reports within their respective interoperability registries and may potentially gain further access to the clinical interoperability registry for additional information, such as the ordering provider and care location, for initiating further investigation.
Key improvements include:
- avoid handwritten forms and data re-entry
- ease transition of data to and from clinical care and public health agencies
- ease transition of data from one public health agency to another
- monitor registries for anomalies in a real-time basis
- response protocols focus on response, not the access to data
Actors/Transaction
There two actors in this profile: Content Creator and a Content Consumer.
Actor Definitions
- Content Consumer
- A content consumer makes use of data contained in.
- Content Creator
- A content creator assembles the data for and produces the document described in
the integration content profile.
Transaction Definitions
To be defined, we await a common content profile template for HL7 CDA R2 based content profiles.
Volume II
Referenced Standards
Document Specifications
Please see the following PDF: ContentProfileForPublicHealthReport.pdf
Open Issues
- Still need to discuss the best way to accomodate a non-human living subject in a CDA.
- What of the proposed here should be fed back to XDS-Lab in the form of CPs?
- How to include attachments (such as images)?
- Do we support the concept of "global specimen id" in the XDS metadata? Can it be queried? For Example: "Find me all documents related to this specimen".