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

Encounter.participant.type name is confusing

XMLWordPrintableJSON

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • STU3
    • Patient Administration
    • Encounter
    • Hide

      PA Virtual WGM Mon Q2 Jan 2021:

      Given that some resources use participant.role (CareTeam), some use performer.function (Procedure), and some use participant.type (Encounter, Appointment), we'd probably need some harmonization guidance from MnM (beyond what Lloyd mentioned in the comments) to determine the pattern that all WGs should apply for documenting participation.

      We do map participant.type to Event.performer.function.

      We spent a decent amount of time discussing role vs. type .vs function and ultimately the distinctions are very subtle and any potential changes to the spec would require more effort than it is worth (both by implementers and the WG).

       

      Show
      PA Virtual WGM Mon Q2 Jan 2021: Given that some resources use participant.role (CareTeam), some use performer.function (Procedure), and some use participant.type (Encounter, Appointment), we'd probably need some harmonization guidance from MnM (beyond what Lloyd mentioned in the comments) to determine the pattern that all WGs should apply for documenting participation. We do map participant.type to Event.performer.function. We spent a decent amount of time discussing role vs. type .vs function and ultimately the distinctions are very subtle and any potential changes to the spec would require more effort than it is worth (both by implementers and the WG).  
    • Cooper Thompson / Irma Jongeneel : 11-0-0

      The name "Encounter.participant.type" name is confusing because it's the type of the participation not the type of the participant. I suggest "role" instead

            Unassigned Unassigned
            GrahameGrieve Grahame Grieve
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: