Stream: implementers
Topic: CapabilityStatements for contained resources, chained params
Ken Sinn (Oct 10 2018 at 13:43):
Hi all,
We are defining CapabilityStatement declarations for a FHIR server.
We are having some trouble with declarations of profiles for contained resources (if necessary at all) .
1) Do contained resource profiles need to be declared at all under CapabilityStatement.profile (STU3) or CapabilityStatement.rest.resource.supportedProfile (R4)? Or is it sufficient to declare them in the profile that's referenced by the parent resource's CapabilityStatement.rest.resource.profile?
2) Is there a way to declare allowed chained search params within CapabilityStatement.rest.resource.searchParam? Or must it be defined via a separate SearchParameter resource? (which only seems to be possible in R4, not in STU3 -- is this correct?)
Thank you!
Lloyd McKenzie (Oct 10 2018 at 14:49):
1. There isn't strictly a need to declare profiles at all. The profile for contained resources would typically be asserted on the element that references the contained resource, though if you have contained resources that are referencing the parent, you'd have to slice the contained element and declare your profiles there. How much profiling you do is really up to you.
2. You define a separate SearchParameter. It should be possible in R3 - where are you running into trouble?
Natalya Pogrebetsky (Oct 15 2018 at 15:00):
Lloyd, for the #2, if I am trying to search for DiagnosticReport profile and I using patient id as a search parameter, do I still need to define Patient ID in a separate SearchParameter resource?
Lloyd McKenzie (Oct 15 2018 at 15:21):
DiagnosticReport already defines a standard patient search criteria
Lloyd McKenzie (Oct 15 2018 at 15:21):
If you're wanting a chained search criteria, you'll need to define that.
Ken Sinn (Oct 15 2018 at 15:28):
If we're looking to enable DiagnosticReport search by the search parameter "patient.identifier=http://something.../hcn|39283483", don't we need to separately define the chained search? since DiagnosticReport search param "patient" is the entire resource itself, not the patient.identifer.
Lloyd McKenzie (Oct 15 2018 at 15:42):
Yes. Patient.identifier would. Patient.id would not - as that's queriable using the patient search criteria.
Christiaan Knaap (Oct 21 2018 at 15:38):
You meant Patient._id?
Lloyd McKenzie (Oct 21 2018 at 19:51):
y
Last updated: Apr 12 2022 at 19:14 UTC
