PDex profiles based on Provenance resource and not US Core Provenance Profile

XMLWordPrintableJSON

    • Type: Comment
    • Resolution: Considered - No action required
    • Priority: Medium
    • US Core (FHIR)
    • 3.1.1
    • Cross-Group Projects
    • US Core Provenance Profile
    • Hide

      The Cross-Group Projects Group reviewed this variance request and suggested that US Core Provenance is sufficient using the claim receipt time as the time recorded in the payer system (this is not the time the Procedure (resource) was performed). The PDex will update to use the US Core provenance profile and add guidance around the recorded time.

      Motion to decline variance - Brett Marquard/Isaac Vetter: 8-0-0

      Show
      The Cross-Group Projects Group reviewed this variance request and suggested that US Core Provenance is sufficient using the claim receipt time as the time recorded in the payer system (this is not the time the Procedure (resource) was performed). The PDex will update to use the US Core provenance profile and add guidance around the recorded time. Motion to decline variance - Brett Marquard/Isaac Vetter: 8-0-0

      PDex defines profiles (and extensions) on the base Provenance resource to allow payers to report provenance of clinical information on a member to meet the requirements of the CMS Interoperability Final Rule.  Since payers are seldom the author of clinical information, they do not have the ability to populate the provenance.recorded element (cardinality 1..1).  We have created profiles that follow the US Core Profile to the extent possible given the use case. We request an exception to the requirement to use a US Core Profile on Provenance for this specific use case.

            Assignee:
            Unassigned
            Reporter:
            Robert Dieterle
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: