Stream: implementers
Topic: Change ProcedureRequest to Service Request
Eric Haas (Sep 13 2017 at 17:44):
GF#13867 proposes a name change from ProcedureRequest to ServiceRequest in response to DSTU notes since the resource covers referrals and procedures. Feedback welcome on the namechange.
Jose Costa Teixeira (Sep 13 2017 at 20:27):
does this mean that procedure resource also changes its name to service?
Jose Costa Teixeira (Sep 13 2017 at 20:27):
I would prefer to see consistency between the request and a corresponding event.
IMO, procedureRequest is to procedure as serviceRequest is to service.
Jenni Syed (Sep 13 2017 at 23:16):
Except that procedureRequest may also be to DiagnosticReport and Observation and ... so, it's already a bit "weird"
Danielle Friend (Sep 13 2017 at 23:19):
And serviceRequest will now represent procedures and referrals. Hence the generic name. It doesn't have a single counterpart
Lloyd McKenzie (Sep 14 2017 at 03:35):
Response to a ServiceRequest could be a Procedure, Observation, Encounter (for a referral) or possibly one or two other things.
Lloyd McKenzie (Sep 14 2017 at 03:36):
So we can't have strict alignment between request and response
Yunwei Wang (Sep 16 2017 at 02:08):
We should specify that in resource's Scope and Usage
Eric Haas (Sep 18 2017 at 14:23):
I think we do. Is there anything specific we should Improve?
Jose Costa Teixeira (Sep 21 2017 at 08:01):
Ok, so it seems that the change of name is to make the request compatible with several types of responses, and Service is an appropriate term, right?
If so, then it makes sense. I was not aware of the rationale.
John Moehrke (Oct 18 2017 at 18:24):
Sorry, I didn't recognize this as a formal query about the appropriateness of ServiceRequest.
Last updated: Apr 12 2022 at 19:14 UTC
