Stream: smart/health-cards
Topic: FHIRVersion
Grahame Grieve (Sep 05 2021 at 21:26):
This:
"fhirVersion": "<<FHIR Version, e.g. '4.0.1'>>"
Should just be 4.0, not 4.0.1. We might issues 4.0.2, for instance, but it would make no difference to consumers or generators of the cards
Max Masnick (Sep 07 2021 at 14:39):
@Josh Mandel is this a change we should make to https://spec.smarthealth.cards/ ?
Josh Mandel (Sep 08 2021 at 15:06):
Perhaps -- we definitely don't want to invalidate existing cards for this purpose though. I think it should be fine from an interoperability perspective for an issuer to say which version of fhir they used all the way down to the patch level; this should not affect validators who only care about the version down to the minor level.
(That said, if we want to update our examples and guidance language in spec.smarthealth.cards to suggest versioning at the minor level instead of the patch level, I am fine with that.)
Josh Mandel (Sep 08 2021 at 17:53):
For comparison, see https://hl7.org/fhir/capabilitystatement-definitions.html#CapabilityStatement.fhirVersion -- it's not clear why we'd want to diverge from this practice/representation which uses values like 4.0.1
Pascal Pfiffner (Sep 09 2021 at 21:28):
I see no issue keeping the patch level, implementers shouldn't do string comparison to check what decoder to use.
Last updated: Apr 12 2022 at 19:14 UTC
