John Moehrke Correction Example
0.1.0 - ci-build
John Moehrke Correction Example, published by John Moehrke (Moehrke Research LLC). This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/JohnMoehrke/correction/ and changes regularly. See the Directory of published versions
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
These define constraints on FHIR resources for systems conforming to this implementation guide.
| Provenance Profile for Corrections |
A profile of the Provenance resource to document corrections made to FHIR data. |
These define sets of codes used by systems conforming to this implementation guide.
| Correction Purposes ValueSet |
A value set of codes representing the purposes for which a correction to FHIR data may be made. |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
| Corrected Condition Example |
An example Condition resource that corrects the error found in version 1. |
| Corrected Food Allergy |
An example AllergyIntolerance resource representing a corrected food allergy record. |
| Corrected Immunization Example |
An example Immunization resource representing a corrected vaccination record. |
| Documentation of Immunization Correction |
A DocumentReference resource providing documentation for the correction made to an immunization record. |
| Dummy Patient example |
Dummy patient example for completeness sake. No actual use of this resource other than an example target |
| Food Allergy Observation |
An example Observation resource representing a food allergy. |
| Immunization Example |
An example Immunization resource representing a vaccination. |
| Initial Condition Example |
An example Condition resource that has an error that version 2 will fix. |
| Provenance for AI Duplicate Detection |
Provenance resource documenting the detection of duplicate FHIR data by an AI system. Where an Observation resources and an AllergyIntolerance were found to be duplicates. Thus the correction removed the Observation, and revised the AllergyIntolerance (updating the AllergyIntolerance with knowledge from the Observation like onset). |
| Provenance for AI Error Detection |
Provenance resource documenting the detection of an error in FHIR data by an AI system. Where Observation was used to record a food allergy, but the AI system detected that this should have been an AllergyIntolerance resource instead. Thus the Observation is removed, and the AllergyIntolerance is created. |
| Provenance for Condition Correction |
Provenance resource documenting the correction made to a Condition resource. Note that the IG does not utilize history/1 and history/2, but this example shows how a correction Provenance would point at the initial incorrect resource and the corrected resource. |
| Provenance for Correction Removal |
Provenance resource documenting the removal of incorrect food allergy observation. This example does not point at a resource that explains the correction, such as a DocumentReference. This use-case also did not replace the concept. |
| Provenance for Immunization Replacement |
Provenance resource documenting the replacement of an immunization record that was in error. This example includes a reference to a DocumentReference that explains the correction. |
| Provenance for Patient Data Erasure Request |
Provenance resource documenting a patient request for data erasure (right to be forgotten). This example shows how the IG for Patient Requested Corrections, which uses DocumentReference to document the request, can be linked to a Correction Provenance that documents the erasure of the Patient resource. The Provenance.agent is the Patient as the data subject requesting the erasure. The Provenance.entity lists ALL of the patient data removed to comply with the request. |
| Provenance for Patient Requested Correction |
Provenance resource documenting a patient requested correction of their birth date. This example shows how the IG for Patient Requested Corrections, which uses Communication to document the request, can be linked to a Correction Provenance that documents the actual correction made to the Patient resource. The Provenance.agent is the Patient as the data subject requesting the correction. |
| Provenance for purging Patient Data due to Age of that data and data retention policies |
Provenance resource documenting the purging of patient data due to the age of that data and compliance with data retention policies. This example shows how the IG for Patient Data Purge can be linked to a Correction Provenance that documents the erasure of the Patient resource and associated data. The Provenance.agent is the Medical Records Officer responsible for ensuring compliance with data retention policies. The Provenance.entity lists ALL of the patient data removed to comply with the data retention policy. |