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

Remove explicit reference to codes and provide an example binding and the choises of codes systems in which concepts can be found.

    XMLWordPrintableJSON

Details

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

      for .agent.type

      Change binding to Preferred 

      Update the valueSet

      • remove the contract signer type codes as not minimally needed and overlapping with existing codes
      • add definitions to the DICOM codes that fit the agent.type use 
      • remove the  RoleCode, RoleClass, participationType

      This leaves ONLY two valuesets from underlying standards (DICOM Audit, and W3C Prov)

      • DICOM codes ( application, app launcher, destination system, source system, destination media, source media)
      • provenance-participant-type (Enterer, Performer, Author, Verifier, Legal Auth, Attester, Informant, Custodian, Assembler, and Composer)

       

      Show
      for .agent.type Change binding to Preferred   Update the valueSet remove the contract signer type codes as not minimally needed and overlapping with existing codes add definitions to the DICOM codes that fit the agent.type use  remove the  RoleCode, RoleClass, participationType This leaves ONLY two valuesets from underlying standards (DICOM Audit, and W3C Prov) DICOM codes ( application, app launcher, destination system, source system, destination media, source media) provenance-participant-type (Enterer, Performer, Author, Verifier, Legal Auth, Attester, Informant, Custodian, Assembler, and Composer)  
    • Lloyd McKenzie / Bill Jacqmein : 10-0-2
    • Correction
    • Non-substantive
    • R5

    Description

      Again, incoherent value set. Many of these codes are 'role' codes - they indicate capacity, not what the agent actually did. They have poor definitions, have duplicates and overlap, no hierarchy across the codes. There are too many codes to map to and no chance there's global concensus that these are the appropriate codes everyone should be mapping to. This must be changed to an example binding to a simplificied value set of actual functions an agent can perform to show the range of possibility (and possibly the choices of code systems in which concepts could be found).

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

      Attachments

        Activity

          People

            john_moehrke John Moehrke
            lloyd Lloyd McKenzie
            Lloyd McKenzie, Ron G. Parker
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: