Stream: patient administration WG
Topic: GF#13195: Add reference to ProcedureRequest to Appointment
Simone Heckmann (Feb 22 2018 at 13:14):
The suggested change was:
"Suggest to add a reference to ProcedureRequest, either by adding a new element or by generalizing the current incomingReferral to "underlyingRequest" (or something along these lines).
The link to a ProcedureRequest (present in both v2 as well as v3) would allow for the linking of the order process with the appointment. Once an MRI has been ordered, there is a subsequent appointment to determine when (and with what MRI) the order should be fulfilled. In imaging workflows this is a common use case, but it probably applies to other requested procedure types as well."
There already is a proposed resolution:
"Include a new property to appointment:
BasedOn 0..* Reference(ProcedureRequest)
(We will be happy for other request types to be included.)"
Simone Heckmann (Feb 22 2018 at 13:19):
In light of the fact that "ReferralRequest and ProcedureRequest have been merged into ServiceRequest".
....I think that makes the whole change request obsolete?
However: renaming Appointment.incomingReferral (ServiceRequest) to something more generic sounds even more like a good idea!
Simone Heckmann (Feb 22 2018 at 13:29):
@René Spronk ...?
Simone Heckmann (Feb 22 2018 at 13:50):
Propose to rename Appointment.incomingReferral to Appointment.basedOn ?
Simone Heckmann (Feb 22 2018 at 13:52):
FYI: I pre-applied the renaming in the current build, but I think we need to re-vote because this changes the resolution from Compatible to Non-Compatible....?
René Spronk (Feb 23 2018 at 10:13):
basedOn sounds good to me. It covers the use case that I brought to the table very nicely.
Simone Heckmann (Feb 28 2018 at 21:09):
resolved 2018/02/28
persuasive
Cooper Thompson/Simone Heckmann:4-0-1
Last updated: Apr 12 2022 at 19:14 UTC
