...
This document is not intended to be a full specification. It does not capture all the required mappings for the Appointment entity, just those that are needed for the timeline view.
Double square bracket notation is used to refer to the PKB Data Model. For example, [[Appointment]] is used to specifically refer to PKB’s concept of an appointment entity, as defined here.
The proposed changes are divided into 2 parts: the changes required for GDE (which require more immediate agreement) and other changes we might make in the future but which do not block development of the FHIR API.
Relevant links
Mappings
The table below shows the proposed end state. Entries in red are different from our current behaviour. Below the table each difference is addressed in more detail.
FHIR | PKB | HL7v2 |
Appointment.status | [[Appointment.Status]] | Based on events received, e.g. SIU S26 would would trigger a status change to “noshow”. |
Appointment.specialty | [[Data Point.Specialty]] (Under discussion) | PV1-10 |
Appointment.appointmentType | [[Appointment.Type]] | SCH-8 |
Appointment.reason | [[Appointment.Reason]] | SCH-7 |
Appointment.description | [[Appointment.Description]] | ? |
Appointment.start | [[Appointment.Start Timestamp]] | SCH-11.4 |
Appointment.end | [[Appointment.End Timestamp]] | SCH-11.5 |
Appointment.comment | [[Appointment.Comment]] | NTE-3 |
Appointment.participant | [[Appointment.Participant]] | WIP |
| [[Appointment.Location]] | PV1-3.9 |
...
Proposed change (future): Upgrade the UI to display the full information stored in [[Appointment.Type]] since it will now be a full CodeableConcept. Reconsider best approach for allowing manual entry of this field, if permitted at all.
Notes: The FHIR HL7 v2 mappings do not seem to cover all the fields we are interested in. Suggest we continue by simply mapping the HL7 v2 “Appointment type” directly to the FHIR “appointmentType”. The datatypes and field names match.
...