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

Appointment participant required valueset contradicts the field definition

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Resolved - change required (View Workflow)
    • Priority: Medium
    • Resolution: Persuasive with Modification
    • Specification:
      FHIR Core (FHIR)
    • Raised in Version:
      STU3
    • Work Group:
      Patient Administration
    • Related Artifact(s):
      Appointment
    • Resolution Description:
      Hide

      Proposed changes to Appointment:

      Update Scope and Usage:

      Appointment resources are used to provide information about a planned meeting that may be in the future or past. The resource only describes a single meeting, a series of repeating visits would require multiple appointment resources to be created for each instance. Examples include a scheduled surgery, a follow-up for a clinical visit, a scheduled conference call between clinicians to discuss a case (where the patient is a subject, but not a participant), the reservation of a piece of diagnostic equipment for a particular use, etc. The visit scheduled by an appointment may be in person or remote (by phone, video conference, etc.) All that matters is that the time and usage of one or more individuals, locations and/or pieces of equipment is being fully or partially reserved for a designated period of time.

      This definition takes the concepts of appointments in a clinical setting and also extends them to be relevant in the community healthcare space, and to ease exposure to other appointment / calendar standards widely used outside of healthcare.

       

      subject 0..1  Reference(Group | Patient) // new field

      participant 1..*

        type  0..*  CodeableConcept

        period 0..1  Period // moved from end of structure

        actor 0..1  Reference(Patient | Group | Practitioner | PractitionerRole | RelatedPerson | Device | HealthcareService | Location)

        required 0..1  Boolean // changed from code

        status  1..1  code

       

      Update Encounter:

      participant 1..*

        type  0..*  CodeableConcept

        period 0..1  Period

        actor 0..1  Reference(Patient | Group | Practitioner | PractitionerRole | RelatedPerson | Device | HealthcareService) // now has additional resource types included (and renamed from individual)

       

      Update AppointmentResponse:

      actor 0..1 Reference(Patient | Group | Practitioner | PractitionerRole | RelatedPerson | Device | HealthcareService | Location) // now has additional resource types included

       

      Show
      Proposed changes to Appointment : Update Scope and Usage : Appointment resources are used to provide information about a planned meeting that may be in the future or past. The resource only describes a single meeting, a series of repeating visits would require multiple appointment resources to be created for each instance. Examples include a scheduled surgery, a follow-up for a clinical visit, a scheduled conference call between clinicians to discuss a case (where the patient is a subject, but not a participant) , the reservation of a piece of diagnostic equipment for a particular use, etc. The visit scheduled by an appointment may be in person or remote (by phone, video conference, etc.) All that matters is that the time and usage of one or more individuals, locations and/or pieces of equipment is being fully or partially reserved for a designated period of time. This definition takes the concepts of appointments in a clinical setting and also extends them to be relevant in the community healthcare space, and to ease exposure to other appointment / calendar standards widely used outside of healthcare.   subject 0..1  Reference(Group | Patient) // new field participant 1..*   type   0..*  CodeableConcept   period 0..1  Period // moved from end of structure   actor 0..1  Reference(Patient | Group | Practitioner | PractitionerRole | RelatedPerson | Device | HealthcareService | Location)   required 0..1  Boolean // changed from code   status   1..1  code   Update Encounter : participant 1..*   type   0..*  CodeableConcept   period 0..1  Period   actor 0..1  Reference(Patient | Group | Practitioner | PractitionerRole | RelatedPerson | Device | HealthcareService) // now has additional resource types included (and renamed from individual)   Update AppointmentResponse : actor 0..1 Reference(Patient | Group | Practitioner | PractitionerRole | RelatedPerson | Device | HealthcareService | Location) // now has additional resource types included  
    • Resolution Vote:
      Andrew Torres/Cooper Thompson: 4-0-1
    • Change Category:
      Enhancement
    • Change Impact:
      Non-compatible

      Description

      Value:

      information-only

      Information Only

      The participant is excluded from the appointment, and might not be informed of the appointment taking place. (Appointment is about them, not for them - such as 2 doctors discussing results about a patient's test).

      Contradicts:

      http://www.hl7.org/fhir/appointment-definitions.html#Appointment.participant

      List of participants involved in the appointment.

      I understand the use-case of 2 providers meeting for consult purposes, but isn't this implementation incorrect? In a resource based scheduling system the patient wouldn't be listed as a participant. It feels like there should be an optional subject/target field. It feels like requried should be a boolean. You either required or not.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              atorres Drew Torres
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Vote Date: