Health Care Survey Reporting Use Case
Table of Contents
- 1 Table of Contents
- 2 Description
- 3 Goals of the Use Case
- 4 Scope of the Use Case
- 4.1 In-Scope
- 4.2 Out-of-Scope
- 5 Use Case Actors
- 6 Health Care Survey Process Abstract Model
- 7 Use Case User Stories and Diagrams
- 7.1 Preconditions
- 7.2 User Stories
- 7.3 Postconditions
- 7.4 Alternate Flow
- 8 Data Requirements
- 9 Policy Considerations
- 10 Non-Technical Considerations
- 11 Appendices
Description
The purpose of the Health Care Survey use case is to identify the hospital (emergency department and inpatient care) and ambulatory care data that will be extracted from EHRs and/or clinical data repositories via FHIR APIs and sent to a system hosted at the federal level. This use case will help define how EHR data can be used in automated data collection, thereby reducing burden for the healthcare provider and EHR with the goal of increasing the submission of timely, quality health care data to the National Center for Health Statistics (NCHS).
Problem Statement
The current ambulatory (manual medical record abstraction) and hospital (claims) data collection method is burdensome for providers, lacks clinical richness, and is inefficient for NCHS.
Goals of the Use Case
Increase the response rate of sampled hospitals and ambulatory health care providers to the National Hospital Care Survey (NHCS) and the National Ambulatory Medical Care Survey (NAMCS)
Increase the volume, quality, completeness, and timeliness of data submitted to the NHCS and NAMCS
Reduce the burden, including cost, associated with survey participation for hospitals, ambulatory health care providers, and data source vendors
Reduce NCHS’s costs associated with recruiting hospital and ambulatory health care providers, and the processing of NHCS and NAMCS data
Develop a complete use case that can be supported by the MedMorph Reference Architecture for the reporting of health care survey data from health care providers and systems to NCHS
Scope of the Use Case
In-Scope
Collect standardized data based on eligibility criteria from NAMCS[1] and NHCS[2] in the hospital and ambulatory care settings
Define under what circumstances a data source system must create and transmit a report to the NCHS data store
Identify the data elements to be retrieved from the data source to produce the report
Collect partial provider-level and all available patient-level data for NAMCS
Collect partial hospital/facility-level and all available patient-level data for NHCS
Out-of-Scope
Assessment of the data quality of the content extracted from the data source
Data captured outside the data source and communicated directly to registries
Changes to existing provider workflow or existing data entry
Policies of the clinical care setting to collect consent for data sharing. (Provider participation in the National Health Care Surveys is by invitation by NCHS based on being selected as part of the nationally representative samples of providers. Consent for participation in each National Health Care Survey is obtained during the manual recruitment process.)
Adult day services centers, residential care communities, nursing homes, home health agencies, and hospice
The National Hospital Ambulatory Medical Care Survey (NHAMCS) is designed to collect data on the utilization and provision of ambulatory care services in hospital emergency and outpatient departments and ambulatory surgery locations. While this IG could be used for NHAMCS data collection, at the present time NCHS is not intending to do so
Use Case Actors
Data Source: A system (e.g., EHR, clinical data repository) used in care delivery for patients which captures and stores data about patients and makes the information available instantly and securely to authorized users. While a data source does contain the medical and treatment histories of patients, a data source system is built to go beyond standard clinical data collected in a provider’s provision of care location and can be inclusive of a broader view of a patient’s care. EHRs are a vital part of health IT and can:
Contain a patient’s medical history, diagnoses, medications, treatment plans, immunization dates, allergies, radiology images, and laboratory and test results
Allow access to evidence-based tools that providers can use to make decisions about a patient’s care
Automate and streamline provider workflow
A FHIR Enabled Data Source exposes FHIR APIs for other systems to interact with the data source and exchange data. FHIR APIs provide well defined mechanisms to read and write data. The FHIR APIs are protected by an Authorization Server which authenticates and authorizes users or systems prior to accessing the data. The data source in this use case is a FHIR Enabled EHR.
Health Data Exchange App (HDEA) MedMorph’s backend services app: A system that resides within the clinical care setting and performs the reporting functions to public health and/or research registries. The system uses the information supplied by the NCHS to determine when reporting needs to be done, what data needs to be reported, how the data needs to be reported, and to whom the data should be reported. The term “backend service” is used to refer to the fact that the system does not require user intervention to perform reporting. The term “app” is used to indicate that it is similar to a SMART on FHIR App which can be distributed to clinical care via the EHR specified processes. The EHR specified processes are followed to enable the Backend Services App to use the EHR's FHIR APIs to access data. The hospital or ambulatory organization is the one who is responsible for choosing and maintaining the HDEA.
National Center for Health Statistics (NCHS) Data Store: A FHIR server or service that receives and stores the health care survey data.
Health Care Survey Process Abstract Model
Figure 1 below is the high-level model that illustrates the actors, activity, and systems involved in Health Care Survey workflow.