Difference between revisions of "201901 Public Health"
(→Roles) |
|||
| Line 43: | Line 43: | ||
==Roles== | ==Roles== | ||
| − | + | ||
| − | + | ===Public Health=== | |
| − | === | + | |
| − | + | Responsible for managing and disseminating trigger codes, decision logic, and knowledge resources. It fosters disease control and prevention programs and activities. | |
| + | |||
| + | ===Public Health Agencies=== | ||
| + | |||
| + | Agencies that receive and manage electronic Initial Case Reports (eICRs), and at times send and/or receive Reportability Responses. Some Public Health Agencies support lifestyle and social services programs. | ||
| + | |||
| + | ===Intermediaries=== | ||
| + | |||
| + | Organizations in the information flow between a health care organization and a public health agency or extra-clinical program. Examples include Health Information Exchanges, the shared platform supported by APHL and CSTE that performs routing, RCKMS decision support and, at times, creates Reportability Responses, etc. | ||
| + | |||
| + | ===Health Care Organization=== | ||
| + | |||
| + | An organization that submits electronic Initial Case Reports (eICRs) based on trigger code matches, and receives trigger code updates and Reportability Responses. Health Care Organizations also report to public health registries and initiate referrals to extra-clinical social services programs. The health care organization can be supported by an EHR vendor in these roles. | ||
| + | |||
| + | ===Social Services and Lifestyle Change Programs=== | ||
| + | |||
| + | Organizations that provide classes, planning, counseling, and/or expertise in the control and prevention of chronic and acute diseases, tobacco cessation, diabetes prevention and others. | ||
| + | |||
| + | ===EHR Document / Report Creator=== | ||
| + | |||
| + | Organization responsible for creating an electronic initial case report (eICR) or another report and sending it to a EHR Document Report Receiver. Examples: EHR vendors and specialty reporting companies. | ||
| + | |||
| + | ===EHR Document / Report Receiver=== | ||
| + | |||
| + | Organization responsible for receiving and processing an electronic initial case report (eICR) and registry submissions. Examples: APHL, public health registry, or a public health agency (PHA). The eICR Document Participant may also play the role of a Reportability Response Document Creator. | ||
| + | |||
| + | ===Reportability Response Creator=== | ||
| + | |||
| + | Organization responsible for creating a Reportability Response (RR) and sending it to a Reportability Response Document Consumer. Examples: APHL or a public health agency (PHA). The Reportability Response Document Creator may also play the role of an eICR Document Participant. | ||
| + | |||
| + | ===Reportability Response Consumer=== | ||
| + | |||
| + | Organization responsible for receiving and processing a Reportability Response (RR). Examples: EHR vendors and specialty reporting companies). The Reportability Response Document Consumer may also play the role of an eICR Document Creator. | ||
==Scenarios== | ==Scenarios== | ||
Revision as of 06:45, 7 December 2018
DRAFT Public Health (Case Reporting, Registries, and Referrals)
Submitting WG/Project/Implementer Group
Public Health (PH) Work Group
Justification
Public health includes a number of use cases involving the exchange of information between Electronic Health Records in clinical care and governmental Public Health Agencies (PHAs) or other extra-clinical organizations. The use cases differ, but they frequently have a number of common design elements as well. Because the data exchange is inherently interorganizational, and because initiating events frequently occur in healthcare, unsolicited “push,” messaging, and other reporting components are important use case needs. This Connectathon will focus on common components like FHIR messaging and clinical infrastructure to support reporting to many different extra-clinical organizations, as well as specific transactions for disease surveillance and chronic disease prevention and management. Electronic case reporting (eCR) has existing CDA product family standards and has a FHIR in-process ballot. This use case will focus on the FHIR subscription dissemination of public health “knowledge distribution” including reporting trigger codes in a PlanDefinition construct and also establishing a path for distribution of reporting criteria and more complex business logic. It will also involve the triggering and creation of the electronic Initial Case Report (eICR) in EHRs, the messaging and exchange of the eICR, and the creation and transmission of Reportability Response information back to providers of care and clinical care reporters as appropriate. The FHIR electronic Case Reporting implementation guide currently in ballot can be found here:
Public health registry reporting shares numerous design elements with electronic case reporting. Some of these elements include the distribution of triggering / reporting rules from public health, appropriate triggering in EHRs, the application of more complex inclusion/exclusion and reporting logic, unsolicited push messaging, supplemental data acquisition, and provider information provisioning. Cancer reporting and others are exploring approaches to implementation that support needed program outcomes from clinical workflow and data and leverage commonalities with other reporting. The CDC Cancer program plans to work on a FHIR physician reporting specification and triggering issues in this Connectathon.
Bidirectional Services eReferrals (BSeRs) are closed-loop exchanges between EHRs in clinical care and mostly extra-clinical social services and lifestyle change programs. There is a FHIR BSeR September ballot with transactions to support the transmission of a referral and response and update communications from the program back to the referring provider. Numerous Centers for Disease Control and Prevention and other agency programs seek to facilitate cessation and prevention programs to increase health and decrease healthcare costs. Unlike referrals between clinicians, specific data segmentation is appropriate to provide these programs relevant data they need without revealing unrelated patient information. The FHIR Bidirectional Services eReferral specification can be found here:
Clinical input requested
Related tracks
Proposed Track Lead
- Rick Geimer
- John Loonsk
- Arun Srinivasan
See Connectathon_Track_Lead_Responsibilities
Expected participants
- Association of Public Health Laboratories
- Centers for Disease Control and Prevention
- Cerner Corporation
- CGI Federal
- Lantana Consulting Group
- Northrup Grumman
- Alliance of Chicago
- YMCAs of America
Roles
Public Health
Responsible for managing and disseminating trigger codes, decision logic, and knowledge resources. It fosters disease control and prevention programs and activities.
Public Health Agencies
Agencies that receive and manage electronic Initial Case Reports (eICRs), and at times send and/or receive Reportability Responses. Some Public Health Agencies support lifestyle and social services programs.
Intermediaries
Organizations in the information flow between a health care organization and a public health agency or extra-clinical program. Examples include Health Information Exchanges, the shared platform supported by APHL and CSTE that performs routing, RCKMS decision support and, at times, creates Reportability Responses, etc.
Health Care Organization
An organization that submits electronic Initial Case Reports (eICRs) based on trigger code matches, and receives trigger code updates and Reportability Responses. Health Care Organizations also report to public health registries and initiate referrals to extra-clinical social services programs. The health care organization can be supported by an EHR vendor in these roles.
Social Services and Lifestyle Change Programs
Organizations that provide classes, planning, counseling, and/or expertise in the control and prevention of chronic and acute diseases, tobacco cessation, diabetes prevention and others.
EHR Document / Report Creator
Organization responsible for creating an electronic initial case report (eICR) or another report and sending it to a EHR Document Report Receiver. Examples: EHR vendors and specialty reporting companies.
EHR Document / Report Receiver
Organization responsible for receiving and processing an electronic initial case report (eICR) and registry submissions. Examples: APHL, public health registry, or a public health agency (PHA). The eICR Document Participant may also play the role of a Reportability Response Document Creator.
Reportability Response Creator
Organization responsible for creating a Reportability Response (RR) and sending it to a Reportability Response Document Consumer. Examples: APHL or a public health agency (PHA). The Reportability Response Document Creator may also play the role of an eICR Document Participant.
Reportability Response Consumer
Organization responsible for receiving and processing a Reportability Response (RR). Examples: EHR vendors and specialty reporting companies). The Reportability Response Document Consumer may also play the role of an eICR Document Creator.
Scenarios
Scenario Step 1 Name
- Action:
- Precondition:
- Success Criteria:
- Bonus point:
