Stream: Da+Vinci+PDex+Plan-Net
Topic: FHIR server Question- Base FHIR resource vs Profile Resource
Bapi Behera (Jan 24 2021 at 15:25):
How the FHIR server manages multiple context use of the FHIR resources? Is it creating multiple roots, maintaining multiple code base to manage multiple context use of FHIR resources?
For example, we have FHIR base insurancePlan resource and also have a PlanNet Insurance Plan (we use base InsurancePlan resource).
1. Are those 2 contexts to be saved in 2 different code base and separate distinct enpoints to call the InsurancePlan resource?
OR
2. Develop one base code for InsurancePlan resource and call the same resource for Plannet InsurancePlan using _profile variable in the URL
@Saul Kravitz @Kate Dech @Mona O
Josh Lamb (Jan 24 2021 at 16:42):
Alignment between profiles used is important for this reason. How is the FHIRBase InsurancePlan profiled? Can you create a resource that will validate against both profiles ? If so you can include both profiles in resource.meta.prpfile[] and share an implementation.
This also assumes that the insurance plan is tracking the same concept between resources.
Josh Lamb (Jan 24 2021 at 16:44):
Is this for cms compliance ?
Ryan Harrison (Feb 06 2021 at 07:00):
@Bapi Behera Concrete examples
ConformanceStatement: Two profiles for the same resource from the same IG.
https://davinci-plan-net-ri.logicahealth.org/fhir/metadata#L14564
"type": "Organization",
"profile": "http://hl7.org/fhir/StructureDefinition/Organization",
"supportedProfile": [
"http://hl7.org/fhir/us/davinci-pdex-plan-net/StructureDefinition/plannet-Organization",
"http://hl7.org/fhir/us/davinci-pdex-plan-net/StructureDefinition/plannet-Network"
],
Resource: The resource.meta.profile[]
key @Josh Lamb mentioned
https://davinci-plan-net-ri.logicahealth.org/fhir/Organization/plannet-organization-cd3a014ba539a78ed4ec0d612#L8
"meta": {
"versionId": "1",
"lastUpdated": "2020-12-21T15:57:42.334+00:00",
"source": "#7ykjXQ06kU83p7g4",
"profile": [
"http://hl7.org/fhir/us/davinci-pdex-plan-net/StructureDefinition/plannet-Organization"
]
},
Josh Lamb (Feb 06 2021 at 20:28):
Organization and network track different concepts. I would be careful to only use the profile that matches the purpose of the data (org or network).
Saul Kravitz (Feb 08 2021 at 13:47):
Take a careful look at the differential view of the two profiles of USCore Organization. The key differences are disjoint values for the 'type' field, and some (MS) extensions, e.g., coverageArea for a network.
Ryan Harrison (Feb 12 2021 at 04:58):
Yes and FFR (for future reference of keyword searchers) by "disjoint values", Saul means the type
ValueSets are non-overlapping.
Recalling that these two ValueSet derive codes from the same CodeSystem.
CodeSystem: http://hl7.org/fhir/us/davinci-pdex-plan-net/CodeSystem-OrgTypeCS.html
- fac
- prvgrp
- payer
- atyprv
- bus
- ntwk
ValueSet: http://hl7.org/fhir/us/davinci-pdex-plan-net/ValueSet-NetworkTypeVS.html
- Bound to
type
in network profile - Includes ONLY ntwk
ValueSet: http://hl7.org/fhir/us/davinci-pdex-plan-net/ValueSet-OrgTypeVS.html
- Bound to
type
in organization profile - Includes the other 5 codes, NOT ntwk
Last updated: Apr 12 2022 at 19:14 UTC