Stream: implementers
Topic: Bundles and Resource Cardinalities
John D. Ament (Jun 11 2020 at 14:00):
My question's in the scope of a SMART on FHIR launch. I'm working with a vendor that is publishing SMART on FHIR widgets and using all Bundle resources to access data, creating fully custom results. Some of the bundles are accessed from my middleware (so they're calling their own FHIR APIs plus mine). One thing we're struggling with is agreeing to the cardinality rules from the FHIR specs. If I'm returning a Bundle of type search-set with a Claim in it, does that Claim need to follow all cardinality rules described in https://www.hl7.org/fhir/claim.html ; for instance the 1..* on the insurance (the vendor represents the insurer so they are actually managing the data for the insurance on the Claim and don't need my system to provide this).
Lloyd McKenzie (Jun 11 2020 at 14:20):
All cardinality requirements as well as all other constraints must be met by all instances in order to be valid. If you think any of the constraints are inappropriate for your use-case , please submit a change request with details about your use-case so the relevant work group can consider whether the constraints should be loosened in a future version. In the meantime, you might be able to use the data-absent-reason extension to satisfy the cardinality. Also consider using the Basic resource.
Lloyd McKenzie (Jun 11 2020 at 14:22):
Note that you can't expect systems that support SMART to support custom query responses - so you'll have to negotiate with any servers you want your app to run on (and I wouldn't hold your breath on most EHR implementers being enthused about supporting custom structures).
Last updated: Apr 12 2022 at 19:14 UTC
