Reconciliation of Clinical Content and Care Providers
The Reconciliation of Clinical Content and Care Providers profile provides the ability to communicate lists of clinical data that were reconciled, when they were reconciled and who did the reconciliation using CDA® constructs and FHIR® Resource attributes.
The Reconciliation of Clinical Content and Care Providers profile provides the structures and transactions needed to communicate the list of reconciled items, when they were reconciled and who did the reconciliation. This can be accomplished with any CDA® or FHIR® constructed list regardless of implementation guide.
The ability to maintain the support of care provision is essential as data is exchanged. This is supported by identifying and examining the heuristics that can be used to facilitate identification of duplicated, overlapping, conflicting or superseded items that may be introduced as a result of sematic interoperability.
Reconciled information is needed to prevent information redundancy and to support clinical care, quality reporting, financial transactions, public health reporting, clinical trials, drug interaction checking, and patient qualification for various protocols. A wide variety of systems will need to reconcile clinical data as information is exchanged, stored and maintained in EMR system or other clinical data repository. This is needed to prevent confusion and conflict of clinical information that can lead to patient safety issues.
This profile provides the ability to communicate lists of clinical data that were reconciled, when they were reconciled and who did the reconciliation
- Systems may (1) create clinical content (2) consume clinical content (3) access clinical information in structured form, perform reconciliation and share resulting reconciled information
Actors & Transactions:
Profile Status: Trial Implementation
<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