Stream: IG creation
Topic: Conformance Expectation at the Resource level
Vassil Peytchev (Nov 22 2021 at 19:41):
The Conformance Expectation extension is defined to be applicable at various levels under Capability Statement, but not directly on the CapabilityStatement.rest.resource level. US-Core is using it at the resource level, and it is prominent in the documentation.
A couple of questions about that:
- What is the meaning of having a conformance expectation on that level?
- Is there an existing Jira ticket to add CapabilityStatement.rest.resource as a valid element for this extension, and if not, is there a need for one?
@Brett Marquard @Eric Haas
Lloyd McKenzie (Nov 22 2021 at 21:15):
Right now, it's not allowed to use capabilitystatement-expectation at the resource level. On FHIR-I, we've determined that there are two possible interpretations for capabilitystatement-expectation on the sub-components of rest.resource (i.e. the different interactions, operations, search parameters, etc.)
- If any of the interactions or operations are SHALL or SHOULD, then the tightest of those apply to the resource as a whole. E.g. if you have resource.search = SHALL for Patient, that means you SHALL support patient, and specifically SHALL support search on patient
- All of the capabilitystatement-expectation declarations on a given resource have an implicit "IF you support the resource, then..." E.g. If you have resource.search = SHALL for patient, that means "IF you choose to support patient, then you SHALL support search on patient"
The question from FMG is, of those IGs that make use of capabilitystatement-expectation, how many use interpretation #1 and how many use interpretation #2
Lloyd McKenzie (Nov 22 2021 at 21:17):
/poll How do you use capabilitystatement-expectation
Option 1 - If there are any SHALLs, you SHALL support the resource
Option 2 - If there are any SHALLs below a resource, they only apply if you choose to support the resource
Option 3 - I never use the capabilitystatement-expectation and I set expectations in text or don't set expectations at all
Grahame Grieve (Nov 22 2021 at 21:24):
Ig's known to use this extension:
Grahame Grieve (Nov 22 2021 at 21:24):
au.csiro.fhir.au-item-715
bcbs.pdexg.fhir.us.com
com.telus.eservices
cqf.fhir.cds4cpm
fhir.argonaut.r2
gene.com.fhir.uapi
healthedatainc.ig-template2
healthedatainc.ig-template4
healthedatainc.sushi-sandbox
hl7.eu.fhir.fair4health
hl7.fhir.it.sandbox
hl7.fhir.us.Davinci-drug-formulary
hl7.fhir.us.bulkdata
hl7.fhir.us.carin-bb
hl7.fhir.us.carin-rtpbc
hl7.fhir.us.cdmh
hl7.fhir.us.central-cancer-registry-reporting
hl7.fhir.us.core
hl7.fhir.us.core.argo
hl7.fhir.us.core.r4
hl7.fhir.us.core.r4validator
hl7.fhir.us.cqfmeasures
hl7.fhir.us.davinci-alerts
hl7.fhir.us.davinci-atr
hl7.fhir.us.davinci-cdex
hl7.fhir.us.davinci-deqm
hl7.fhir.us.davinci-deqm.stu3
hl7.fhir.us.davinci-drug-formulary
hl7.fhir.us.davinci-hrex
hl7.fhir.us.davinci-notifications
hl7.fhir.us.davinci-pdex
hl7.fhir.us.davinci-pdex-NatlDir
hl7.fhir.us.davinci-pdex-NatlDirExch
hl7.fhir.us.davinci-pdex-plan-net
hl7.fhir.us.davinci-ra
hl7.fhir.us.fhir-medmorph
hl7.fhir.us.fhir-registry-protocols-ig
hl7.fhir.us.health-care-surveys-reporting
hl7.fhir.us.insurance-card
hl7.fhir.us.mcode
hl7.fhir.us.medmorph
hl7.fhir.us.meds
hl7.fhir.us.pacio-adi
hl7.fhir.us.pacio-cs
hl7.fhir.us.pacio-fs
hl7.fhir.us.pacio-rat
hl7.fhir.us.pacio-reassessment-timepoints
hl7.fhir.us.pacio-rt
hl7.fhir.us.patient-reported-outcomes
hl7.fhir.us.patient-reported-outcomes-21cfr11
hl7.fhir.us.saner
hl7.fhir.us.sdoh-clinicalcare
hl7.fhir.us.skinwoundassessment
hl7.fhir.us.specialty-rx
hl7.fhir.uv.bulkdata
hl7.fhir.uv.fhir-radiation-dose-summary-ig
hl7.fhir.uv.fhir-saner
hl7.fhir.uv.immds
hl7.fhir.uv.ipa
hl7.fhir.uv.radiation-dose-summary
hl7.fhir.uv.saner
hl7.fhir.uv.sdc
hl7.fhir.uv.vhdir
hl7.org.fhir.cdisc-lab
hl7.org.fhir.us.cdisc-lab
hl7.org.fhir.us.cdl
hl7.org.fhir.uv.cdisc-lab
hl7.org.fhir.uv.cdisc-lab.2019Sep
l7.fhir.us.davinci-alerts
labcorp.fhir.ngs-cds
openimis.fhir.r4
openmhealth.mfhir
Eric Haas (Nov 24 2021 at 18:52):
- almost everything in the IG capability statement is an expectation. It is telling implementers how to implement the ig.
- yes
Eric Haas (Nov 24 2021 at 18:57):
We are trying to make this resource useful and approachable to implementers.
Vassil Peytchev (Nov 24 2021 at 20:32):
@Eric Haas , wouldn't your approach fit option 4 above?
Last updated: Apr 12 2022 at 19:14 UTC
