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

ProvenanceActivityType should not be an extensible value set

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • FHIR Core (FHIR)
    • R4
    • Security
    • Provenance
    • Hide

      change .activity:

       

      Show
      change .activity: change to Example binding Bring in 6-10 example codes 21089 lifecycle amend originate merge deidentify receive transform verify update narrative to explain this is a sample update narrative to point at some of the existing valuesets as potentially useful valuesets for IG or implementations. http://terminology.hl7.org/CodeSystem/v3-DocumentCompletion   http://terminology.hl7.org/CodeSystem/v3-DataOperation    
    • Lloyd McKenzie / Joe Lamy : 7-0-0
    • Correction
    • Compatible, substantive
    • R5

    Description

      Again, this value set is incoherent. It's not a proper value set at all - it's a grab-bag of all sorts of things. Statuses are not 'events'. There are duplicates and overlaps. The set of codes is too large and unstable for reasonable mapping to be done and there's no chance there's global consensus on mapping to this. The value set itself should be example and should be simplified to indicate the 'kinds' of events that might appear.

      (Comment 79 - imported by: Ron G. Parker)

      Attachments

        Activity

          People

            Unassigned Unassigned
            lloyd Lloyd McKenzie
            Lloyd McKenzie, Ron G. Parker
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: