Stream: implementers
Topic: DSTU2 Appointment Role
Dave Barnet (Sep 21 2017 at 11:14):
Sorry to go back to DSTU2! I'm trying to represent participants in an appointment in DSTU2. In particular I'm trying to represent a Chaperone and an Advocate (which I'm assuming will be a RelatedPerson). In the DSTU2 appointment, the participant types are tied down to the http://hl7.org/fhir/ValueSet/encounter-participant-type list (i.e. required), which doesn't support detail. Even this list in RelatedPerson.relationship (which isn't the correct place to model this data!) is tied down to the http://hl7.org/fhir/ValueSet/relatedperson-relationshiptype, which mostly covers blood and non-blood relatives, but not chaperone or advocate. Has anyone else encountered this problem in DSTU2, and if so what was the solution. I know that STU3 has made the Appointment.paticipant.type extensible, but this is a project in DSTU2.
Lloyd McKenzie (Sep 21 2017 at 15:19):
Chaperone could be a RelatedPerson or a Practitioner (depending on whether it's someone from the clinic acting in their professional capacity or someone the patient brings along). Unfortunately in DSTU2, your only way around the brokenness of it being 'required' is to use an extension and omit type.
Last updated: Apr 12 2022 at 19:14 UTC
