Vital Records Death Reporting
Vital Records Death Reporting defines a Retrieve Form for Data Capture (RFD) content profile that will specify derivation of source content from a medical summary document. by defining requirements for form filler content and form manager handling of the content.:
The Vital Records Death Reporting Content Profile supports pre-population of data from electronic health record systems to electronic vital records systems for death reporting to meet Federal, state and local reporting requirements.
- Establishes interoperable electronic exchange of VR data between EHR and VR Systems
- More timely data release
- Higher quality data for demographic and epidemiologic surveillance and research
- Less costly electronic vital registration systems
- Greater integration with other stakeholder electronic systems
- Greater standardization of electronic Vital Records data collection and exchange
Vital statistics data are the basis for national and state information relevant for promoting public health and for aiding decision makers in setting policies, directing resources, managing problems, and identifying emerging health trends. Vital Records Death Reporting is part of the process of creating the legal record of a person’s death. The provider caring for the patient at the time of death is responsible for reporting medical details on death. Some of the information that is to be reported in the death record exists within the EHR. This profile will define an RFD-based content profile that will specify derivation of source content from a medical summary document. The profile will define requirements for form filler content and form manager handling of content.
- EHR Systems
- Electronic Death Registration Systems (EDRS)
- Infrastructure (Forms Manager)
'Trial Implementation: http://www.ihe.net/uploadedFiles/Documents/QRPH/IHE_QRPH_Suppl_VRDR.pdf
<Provide direct links to the specific volumes or supplements, and list the volume sections relevant to this profile. This is a simple inventory of official normative and informative text. If you would like to provide a reading guide or walkthrough of what is in each of the different sections for implementers or users, do that in the Profile FAQ or the Profile Implementation Page linked below. If the profile uses transactions from multiple Tech. Frameworks, repeat the structure below.>
<list all the standards on which the profile is based; if possible with links to sources>
<The following sections can be left out if there is nothing to point to. This is just to show where such information can go.>
<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one. Start with the name of the other profile as a link and then explain the relationship.>
- Reporting Workflow [RWF] may use Evidence Documents as inputs to the reporting process.
- Simple Image & Numeric Reports [SINR] may include data copied from Evidence Documents.
- Cross-enterprise Document Sharing for Imaging [XDS-I] can be used to share Evidence Documents between sites over a network.
- Portable Data for Imaging [PDI] can store Evidence Documents on media such as CDs.
- Import Reconciliation Workflow [IRWF] can fix patient ids, etc. of Evidence Documents when importing.
The Profile FAQ Template answers typical questions about what the Profile does. <Replace the link with a link to the actual FAQ page for the Profile>
The Profile Purchasing Template describes considerations when purchasing equipment to deploy this Profile. <Replace the link with a link to the actual Purchasing page for the Profile>
The Profile Implementation Template provides additional information about implementing this Profile in software. <Replace the link with a link to the actual Implementation page for the Profile>
<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis). Go ahead, Google: IHE <Profile Name> abstract or Google: IHE <Profile Name> and under the "more" select "Scholar". You might be surprised. >
This page is based on the Profile Overview Template