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

Add additional codes to http://hl7.org/fhir/ValueSet/provenance-activity-type

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Applied (View Workflow)
    • Priority: Medium
    • Resolution: Persuasive with Modification
    • Specification:
      FHIR Core (FHIR)
    • Raised in Version:
      STU3
    • Work Group:
      Security
    • Related Artifact(s):
      Provenance
    • Related Page(s):
      Terminologies - Valuesets
    • Related Section(s):
      4.4.1.200
    • Grouping:
    • Resolution Description:
      Hide

      Modify provenance-activity-type

      Show
      Modify provenance-activity-type Add http://hl7.org/fhir/ValueSet/object-lifecycle-events Thus remove iso-21089-lifecycle as it is included above Add all of  http://terminology.hl7.org/CodeSystem/v3-DocumentCompletion   where there is only LA included today Add all of http://terminology.hl7.org/CodeSystem/v3-DataOperation   where there is a REST subset today. Seems some of these are duplicates with lifecycle events. Should we really duplicate lifecycle events? Add ObligationPolicy subset of  http://terminology.hl7.org/CodeSystem/v3-ActCode where there is a subset pulled today, all seem useful Add all   http://terminology.hl7.org/CodeSystem/v3-ActStatus   Add all FHIR Event status http://hl7.org/fhir/event-status  
    • Resolution Vote:
      Kathleen Connor / Carie Hammond: 7-0-0
    • Change Category:
      Enhancement
    • Change Impact:
      Compatible, substantive

      Description

      The ProvenanceActivityType definition states that: "This value set contains representative Activity Type codes, which includes codes from the HL7 DocumentCompletion, ActStatus, and DataOperations code system, W3C PROV-DM and PROV-N concepts and display names, several HL7 Lifecycle Event codes for which there are agreed upon definitions, and non-duplicated codes from the HL7 Security and Privacy Ontology Operations codes."

      However, the representative codes are very limited and may confuse implementers. For example, there are no links to the LCE codes https://www.hl7.org/fhir/valueset-object-lifecycle-events.html, all of which should be included in this representative value set.

      Important v3-DataOperations codes are missing, e.g., execute, perhaps because of the thought that classic RESTful Operations don't include execute. However, the Provenance.activity could be conducted outside of the RESTful paradigm.

      There are few activities listed in Act.code http://build.fhir.org/v3/ActCode/cs.html. Even the ObligationPolicy codes are about the requirement to do an act. Perhaps this value set should be removed from Provenance Activity Type value set. Check to see that these required activities are included elsewhere as "activities". E.g., in https://www.hl7.org/fhir/valueset-object-lifecycle-events.html

      ActStatus http://terminology.hl7.org/CodeSystem/v3-ActStatus has several that should be added, e.g., completed, held, aborted, nullified, suspended, and obsolete.

      All of the DocumentCompletion codes should be included. http://build.fhir.org/v3/DocumentCompletion/cs.html

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              john_moehrke John Moehrke
              Reporter:
              k.connor Kathleen Connor
              Request in-person:
              John Moehrke, Kathleen Connor
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Vote Date: