Stream: implementers
Topic: Priority for a procedure that should be done
René Störmer (Oct 21 2020 at 07:57):
A surgical procedure should take place for a patient. Before this is done, a ServiceRequest is produced, requesting that Procedure. Before setting the Appointment for that Procedure we need to know the priority , to determine how the priority compares to other Appointments that still have to be planned or are already planned.
Where would you track this?
For me the ServiceRequest would be the most logical place, as this would specify the priority of the request (A Procedure or Appointment might not exist yet). The problem is, that the ServiceRequest only allows routine | urgent | asap | stat as values. From our customers we get different and more values (Also differs between customers). A CodeableConcept would therefore be more appropriate, or at least the possibility to use other values, because by mapping to routine | urgent | asap | stat we would lose information.
Any ideas?
Jose Costa Teixeira (Oct 21 2020 at 11:33):
Do you mean the "urgency" of the request as seen by the requester, or the priority that is assigned by the performer?
For example we can have 2 urgents, but only one would be the first one to be answered.
Jose Costa Teixeira (Oct 21 2020 at 11:34):
if you mean the urgency as seen by the requester, i.e. not knowing if that urgency is going to be respected by the performer, we would typically expect a finite set of priority levels.
Jose Costa Teixeira (Oct 21 2020 at 11:35):
I think the current value set is standard
Jose Costa Teixeira (Oct 21 2020 at 11:35):
I do not know if there is a reason why this binding is required shouldn't be preferred (possibly because allowing different values is a great way to mess up screening and assigning)?
Last updated: Apr 12 2022 at 19:14 UTC
