Unclear how provenance is handled in this IG - MCODE #1

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • US Minimal Common Oncology Data Elements (mCODE) (FHIR)
    • STU3
    • Clinical Interoperability Council
    • (NA)
    • Hide

      We could have done a better job explaining that, as a FHIR IG, mCODE relies on all the same mechanisms that FHIR uses for recording and tracking provenance. This isn't an area where mCODE is trying to do better than, or go beyond, what is provided in FHIR, even in areas where FHIR is less than perfect.

      The proposed resolution is to add a paragraph explaining how mCODE relies on FHIR for recording and tracking provenance, and point to appropriate references.

      Proposed resolution: Persuasive with mod

      Show
      We could have done a better job explaining that, as a FHIR IG, mCODE relies on all the same mechanisms that FHIR uses for recording and tracking provenance. This isn't an area where mCODE is trying to do better than, or go beyond, what is provided in FHIR, even in areas where FHIR is less than perfect. The proposed resolution is to add a paragraph explaining how mCODE relies on FHIR for recording and tracking provenance, and point to appropriate references. Proposed resolution: Persuasive with mod
    • Richard Esmond/Kurt Allen: 10-0-1
    • Clarification
    • Non-substantive

      Comment:

      Not clear if/how provenance is represented in this FHIR Implementation Guide. Provenance (who, what, when, where, why) is essential at: 1) point of origination (at the source, for newly captured content), 2) point of update (for newly updated content, preserving previous content and its provenance).

      Who = subject of care/information (typically the patient)

      Who = performer of action taken

      Who = author of information captured or updated

      Who = organization

      What = action taken

      When = date/time of action taken

      When = date/time of information capture or update

      Where = physical location of action taken

      Where = physical location of information capture or update

      Where = network address and/or device ID where information captured or updated

      Why = rationale, purpose of action taken

      Why = rationale, purpose of information capture or update

      Granularity of provenance (e.g., binding authorship to content) may be at the dataset or element level.

      Summary:

      Unclear how provenance is handled in this IG

            Assignee:
            Mark Kramer
            Reporter:
            Gary Dickinson
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: