Stream: implementers
Topic: Procedure.status for future procedure
Yunwei Wang (Jul 02 2019 at 15:56):
I am trying to create instances for scheduled procedure. (eg: Patient will have this surgery next week.) So I have a Procedure which is referenced in an Appointment. What is the status for this Procedure? I feel that the only value I can use is "unknown" (http://hl7.org/fhir/valueset-event-status.html).
Chris Moesel (Jul 02 2019 at 16:17):
I don't think unknown would be appropriate, as the spec says:
The "unknown" code is not to be used to convey other statuses. The "unknown" code should be used when one of the statuses applies, but the authoring system doesn't know the current state of the procedure.
In my opinion, I'd use preparation. It's a decent match if you have a liberal reading of the term "staging activities" -- and the fact that it maps to the canonical status planned makes me think it is probably the most appropriate status for what you're describing.
Yunwei Wang (Jul 02 2019 at 16:24):
That was my first choice. Then I was kindly backed off. Yes Planned is more accurate. Call it Preparation is a little bit strange.
John Silva (Jul 02 2019 at 17:41):
The Workflow model has a Task resource which has intent with 'plan' as a value. This is where it would be nice to have consistency between the workflow-related resources and the Workflow 'model'. http://hl7.org/fhir/valueset-task-intent.html
Lloyd McKenzie (Jul 02 2019 at 17:52):
Procedure should only come into existence when some sort of work has actually started on it. Until then, you just have Appointment and/or ServiceRequest. Procedure.status of 'preparation' is for things like pre-op tests or registration or getting the surgical suite ready before the patient shows up.
Yunwei Wang (Jul 02 2019 at 18:39):
@Lloyd McKenzie But Appointment.reasonReference can reference to a procedure. "Reason the appointment has been scheduled to take place, as specified using information from another resource."
And what you said was my understanding. But then the EventStatus value set (http://build.fhir.org/valueset-event-status.html) states that "preparation" is ~planned.
Lloyd McKenzie (Jul 02 2019 at 18:49):
If you're booking an appointment because of a Procedure, it's because of the results of the previous procedure, not because of a planned procedure. (The latter would be handled by pointing to a ServiceRequest.) Preparation is the 'planning' stage - it's getting stuff ready. But it's an "Event" resource, which means that it doesn't begin until you're doing something. All ordering/proposing/planning where nothing's been done yet is handled using Request resources.
Yunwei Wang (Jul 02 2019 at 20:25):
@Lloyd McKenzie That makes senses. But ServiceRequest was introduced in R4, what is the equivalent in STU3 and DSTU2?
Eric Haas (Jul 02 2019 at 20:42):
Proc request
Last updated: Apr 12 2022 at 19:14 UTC
