Stream: implementers
Topic: Different profiles for POST and GET
Barbro Vessman (Oct 28 2021 at 14:36):
Would it be a bad idea to have different profiles for one resource type, depending on the method used, in this case GET versus POST?
The business rules aren't quite the same and we would like to validate against the profile to check that the resource is OK . Or any ideas on how to achieve that, keeping just one profile?
Vassil Peytchev (Oct 28 2021 at 14:42):
Is the difference between Read and Create, or between the two different ways to execute a Search?
Barbro Vessman (Oct 28 2021 at 15:06):
It is between Read and Create
Lloyd McKenzie (Oct 28 2021 at 15:30):
It's totally fine to say that what you accept in and what you provide out are slightly different. You might allow stuff through your front door that you don't support (and will throw away) and you may supplement information you've received or may have data from other sources that will have different behavior than what you take in over your FHIR interface.
Lloyd McKenzie (Oct 28 2021 at 15:31):
That said, CapabilityStatement doesn't provide good ways of making these distinctions, so you'd be looking at some sort of supplemental documentation/extensions to point at differentiated profiles per operation.
Lloyd McKenzie (Oct 28 2021 at 15:31):
(Note that Vassil's question is because search can happen via POST in addition to GET.)
Grahame Grieve (Oct 28 2021 at 23:00):
US core has different profiles for read and write on some elements
Shamil Nizamov (Oct 29 2021 at 00:08):
Like what other than mandatory write for the DocumentReference and DiagnosticReport (for Notes)?
Grahame Grieve (Oct 29 2021 at 00:09):
I think the mime types supported are different for read and write
Eric Haas (Oct 29 2021 at 04:02):
in US Core we have focused on read and search and don't have separate profiles for writes. In the Argonaut Argo-write project we have discussed making 'mixin' profiles ( my term) to add the stuff we think is useful for client writes to EHR on top of a US Core profile. In other words the union of 2 profile like an Observaition write 'mixin' profile + US Core Weight. This is untested and not settled.
Barbro Vessman (Oct 29 2021 at 06:53):
Great answers, thanks everyone!
Last updated: Apr 12 2022 at 19:14 UTC
