-
Notifications
You must be signed in to change notification settings - Fork 156
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
issue #3192 - omit breaking types from 4.0.1 CapabilityStatement
In the current draft of FHIR R4B, the following resource types have backwards-incompatible changes: * DeviceDefinition * Evidence * EvidenceVariable Now these resource types will be omitted from the FHIR 4.0.1 version of our CapabilityStatement (similar to the types that are newly added in R4B). Based on https://chat.fhir.org/#narrow/stream/179166-implementers/topic/R4B.20compatibilty/near/269414612, I left a TODO in the code about whether to remove ActivityDefinition and PlanDefinition from the 4.0.1 flavor of the CapabilityStatement as well. At least for now, they are still advertised and should work for R4 clients just fine (so long as there's no R4B instances that use the new subjectCanonical choice type). Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
- Loading branch information
Showing
2 changed files
with
14 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters