Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-35697

Tools to capture errors or discrepancies are needed

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Highest Highest
    • US Health Care Surveys Reporting Content Implementation Guide (FHIR)
    • 0.1.0
    • Public Health
    • Use Cases
    • 2 Use Cases
    • Hide

      We agree with the commenter that there are data quality issues with EHR data at present time. However, although these concerns are valid, the concerns transcend the IG and are out of scope for this IG. Syncing on US Core Profiles that map to USCDI at least partially addresses the concerns raised here because it is expected that all implementers will incrementally improve on data quality over time because of this standardization. The validation step in the workflow diagram is just ensuring the FHIR data structure is valid. Also, NCHS has existing processes to validate and or edit data received at the PHA. These processes will be adjusted for data that comes from EHRs that is informed by this IG.

      Show
      We agree with the commenter that there are data quality issues with EHR data at present time. However, although these concerns are valid, the concerns transcend the IG and are out of scope for this IG. Syncing on US Core Profiles that map to USCDI at least partially addresses the concerns raised here because it is expected that all implementers will incrementally improve on data quality over time because of this standardization. The validation step in the workflow diagram is just ensuring the FHIR data structure is valid. Also, NCHS has existing processes to validate and or edit data received at the PHA. These processes will be adjusted for data that comes from EHRs that is informed by this IG.
    • Becky Angeles / Craig Newman : 25-0-3

    Description

      One of the stated intents of this IG is to reduce the burden of data collection and curration by users and systems by automating the process. At this stage of EHR evolution, the collection of data in a particular system and compatibility of that data to supposedly "like" or "similar" data from other sysetems is not guaranteed, even internally the data may require "cleansing" to arrive at a useful level of specification for research purposes. To identify and correct data quality/integrity issues at this stage of EHR evolution, tools to capture errors or discrepancies for correction should be employed to refine the capability of the sytem to reduce the workload required for error detection and correction by the users and the system itself.

      Existing Wording:

      Out of Scope: Validation of the EHR data.

      Proposed Wording:

      Reconcile this statement with the validation steps that occur in the flow diagrams-

      (Comment 1 - imported by: Chris Shawn)

      Attachments

        Activity

          People

            Unassigned Unassigned
            klsalzman Keith Salzman
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: