Stream: argonaut
Topic: US Core Location
Yunwei Wang (Dec 20 2021 at 15:54):
According to US Core Server CapabilityStatement, server SHALL support US Core Location.
According to US Core General Guidance, a reference to Location SHOULD be US Core Location.
That creates an interesting situation that when US Core Encounter references a Location, according to Server CapabilityStatemeent, the reference Location resource SHALL be US Core Location and according to General Guidance, the referenced Location resource MAY be a FHIR resource.
Is that correct?
Or should the Server CapabilityStatement be interpreted as "Server is required to support US Core Location but MAY also support FHIR Location resource additionally. Client SHALL check meta.profile to verify the actual profile. If meta.profile is empty, client MAY treat the resource as a FHIR Location resource."
Then, should the US Core Location's CapabilityStatement.rest.resource.supportedProfile include both USCore profile and FHIR profile?
Vassil Peytchev (Dec 20 2021 at 16:10):
Is there a specific FHIR profile on Location? If not, the base specification is assumed to be supported for all resources, isn't it?
Yunwei Wang (Dec 20 2021 at 16:32):
If I have a server which claim to be US Core conformant, is it a problem that my Location endpoint provides base FHIR location resource instead of US core Location resource?
Eric Haas (Dec 20 2021 at 16:37):
Remember the US Core Server CapabilityStatement, server states SHALL must support Patient +1 so if you support location use it everywhere.
Eric Haas (Dec 20 2021 at 16:40):
We pulled back on practitionerrole and location to base FHIR since we did not have consensus there for US Core. Hence the guidance
Eric Haas (Dec 20 2021 at 16:46):
as far as base profile in supported profile in capability statement - no. A fhir server may have a profile in CapabilityStatement.rest.resource.profile for Location that is different from the base Location. See : http://build.fhir.org/profiling.html#profile-uses
Last updated: Apr 12 2022 at 19:14 UTC
