Reconciliation of Clinical Content and Care Providers (RECON)
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.
Summary
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.
Benefits
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.
Details
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 Affected
- 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:
Specification
Profile Status: Trial Implementation
Documents: RECON profile
See Also
<The following sections can be left out if there is nothing to point to. This is just to show where such information can go.>
This page is based on the Profile Overview Template