Stream: Orders and Observation WG
Topic: ServiceRequest status: stopped?
Travis Stenerson (May 09 2018 at 15:05):
I'm curious as to why there is no equivalent status on a procedure request as there is on a medication request for a started but stopped service. Currently, there would be no way of determining if a request was terminated after initiation or before initiation. This also somewhat pertains to the potential addition of (something like) Dosage to these requests. Should I submit a tracker about this or has there been previous discussion?
This also somewhat pertains also to RequestGroup. Thank you
Lloyd McKenzie (May 09 2018 at 15:12):
@Michelle (Moseman) Miller ?
Eric Haas (May 09 2018 at 15:16):
The statused are aligned with the request pattern statuses...
- cancelled Cancelled The authorization/request to act has been terminated prior to the full completion of the intended actions. No further activity should occur.
there is no status in the pattern to indicate it was stopped before it was started but is that even a thing?
What is a use case for this?
Eric Haas (May 09 2018 at 15:16):
@Lloyd McKenzie did you discuss in workflow?
Eric Haas (May 09 2018 at 15:18):
@Melva Peters did you get a nastygram from workflow regarding your status not being in alignment re this?
Lloyd McKenzie (May 09 2018 at 15:19):
Pharmacy has dispensation for "stopped" rather than "aborted".
Lloyd McKenzie (May 09 2018 at 15:20):
In Procedure, if something wasn't done at all, it would have a status of not-done. If it had been started, then stopped, it would be aborted.
Eric Haas (May 09 2018 at 15:27):
Code
draft
active
suspended
cancelled
completed
entered-in-error
unknown
Eric Haas (May 09 2018 at 15:27):
request statuses
Eric Haas (May 09 2018 at 15:28):
for ServiceRequest
Travis Stenerson (May 09 2018 at 15:32):
I was looking more at request group, for returning a set of surveillance type requests (PSA every 6 months, Prostate biopsy every 12 months). I guess it kind of leads to another question. What is the status of a request that doesn't have a specified end date but is expected to terminate when something changes in the patient? Is that even a thing?
Eric Haas (May 09 2018 at 15:38):
active
Travis Stenerson (May 09 2018 at 16:11):
Sorry Eric, I meant after that event occurs (in this case it would be worsening of the cancer).
Eric Haas (May 09 2018 at 16:20):
I havent looked at RequestGroup very much so need to defer that question to someone else, perhaps @Bryn Rhodes ?
Lloyd McKenzie (May 09 2018 at 18:44):
A request that's triggered (or terminated) conditionally would be "active" as soon as the authoriation is in place. As a simple example, if I write a prescription today (May 2018) that says "Starting June 1, patient should take 1 tablet twice a day", the order is "active" today (from the moment it's signed), even though the patient isn't supposed to start - and dispenses might not even be allowed for 1.5 months. On the other hand, the MedicationStatement which reflects what the patient is actually doing shouldn't go active until July.
Last updated: Apr 12 2022 at 19:14 UTC
