Stream: implementers
Topic: Validity period of a service request
Robin Bosman (May 27 2020 at 16:10):
A ServiceRequest would typically be valid until a certain date. What would be exact meaning behind ServiceRequest.occurence - that is defined as "When service should occur"? - what if a ServiceRequest would be fulfilled after the date set in .occurence, should that be a problem? How to define a ServiceRequest shall be fulfilled by a certain date after which date is it no longer supposed to be used?
Lloyd McKenzie (May 27 2020 at 16:12):
A ServiceRequest represents an authorization. If something is done that's outside what's described by the ServiceRequest, then it technically doesn't fall within the scope of the authorization. In practice, there tend to be business rules and some degree of professional discretion around variation - and how much variation is permitted before you get in trouble for doing something without appropriate authorization.
Robin Bosman (May 28 2020 at 07:03):
Tx! On a related note: if I want to know when the thing that was authorized by the ServiceRequest was actually done I would look for the .basedOn in the Procedure/Observation/... that refers to that ServiceRequest , right?
Vassil Peytchev (May 28 2020 at 12:59):
If both the ServiceRequest and the thing that was authorized are recorded in the same system, then most likely the .basedOn will refer directly to the original ServiceRequest. If the observation/procedure was performed in a different system, the .basedOn may be referencing a local copy or modified instance of the ServiceRequest, which in turn will have .basedOn referencing the original.
Robin Bosman (May 28 2020 at 14:18):
That is very clear - tx for the extra details you provided in your answer!
Last updated: Apr 12 2022 at 19:14 UTC
