Details
-
Change Request
-
Resolution: Persuasive
-
Highest
-
Canonical Resource Management Infrastructure (FHIR)
-
1.0.0-ballot [deprecated]
-
Clinical Decision Support
-
Distribution
-
8.4
-
-
Floyd Eisenberg/Greg White: 13-0-0
-
Correction
-
Compatible, substantive
Description
New extensions are being introduced all the time that could be dependencies that will need to be traced. You can't presume that cpg extensions will be the only ones that matter. We need an extension we can put on an extension definition of type canonical that indicates whether it's a dependency that should be traced when packaging. We also need an explanation of what the rules are for deciding whether to set that to true or not. I.e. what were the rules used to come up with the current list? Can we be confident that all packaging consumers will want the same rules followed? (E.g. might some want code systems, but others be satisfied with value sets?)
(Comment 54 - imported by: Lloyd McKenzie)
Attachments
Issue Links
- is voted on by
-
BALLOT-52239 Negative - Lloyd McKenzie : 2023-Sep-FHIR IG CRMI R1 STU
- Withdrawn