FHIR Chat · Appointment - more supporting and outcome data · implementers

Stream: implementers

Topic: Appointment - more supporting and outcome data

Vijay Thangavelu (Mar 13 2018 at 15:29):

Team,

We have use-cases to document Patient's Appointment detail with reason, outcome and rescheduled data.

below are few data elements we have clarification as we couldn't map to Appointment resource directly,

1. planned transportation - it will be free text to record what mode of transportation patient use.
does it make sense to have extension in Appointment.participant

2. if in case, the appointment has been rescheduled, we would like to handle that in the same appointment with different status, but with current status list we don't see a appropriate mapping. is there a different way to handle reschedule, like separate/new appointment?

3. Appointment outcome - we also have few followup documentation once the appointment is completed.
below are few sample data,

We were thinking to map these information in Appointment.supportingInfo

 1. Candidate for Permanent Access Surgery
 2. Vessel Mapping Completed at this appointment
 3.  Additional Consult Needed
 4. Follow up  Medical Clearance needed

Would it make sense to put the above data in DiagnosticReport/Observation (each element is an observation) or QuestionnaireResponse?

Appointment.supportingInfo --> DiagnosticReport --> Observation
Appointment.supportingInfo --> QuestionnareResponse

Please advice.

Thanks,
Vijay

Lloyd McKenzie (Mar 13 2018 at 16:19):

@Brian Postlethwaite ?

Vijay Thangavelu (Mar 14 2018 at 19:33):

one more clarification, this might be simple.
if an Appointment outcome lead to a Procedure, is there a way to reference the Procedure and the Appointment.

currently one option we have is, referencing it through Encounter

Procedure --> Encounter --> Appointment

But looking to avoid creating Encounter in this context if possible, any other better option?

Please Advice.

Thanks,
Vijay

Lloyd McKenzie (Mar 14 2018 at 21:20):

You could certainly submit a change request asking for Procedure to be able to be "basedOn" an Appointment, not just a ServiceRequest or CarePlan

Vijay Thangavelu (Mar 14 2018 at 23:01):

Thanks @Lloyd McKenzie , will do.

Last updated: Apr 12 2022 at 19:14 UTC