Details
-
Change Request
-
Resolution: Persuasive with Modification
-
Medium
-
FHIR Core (FHIR)
-
R4
-
FHIR Infrastructure
-
OperationDefinition
-
-
Paul Denning/Josh Mandel: 12-0-0
-
Correction
-
Non-substantive
-
R5
Description
opd-3 restricts using OperationDefinition.parameter.targetProfile only when OperationDefinition.parameter.type is a reference or canonical. https://jira.hl7.org/browse/FHIR-26411 suggests that OperationDefinition.parameter.type can be a resource and still use OperationDefinition.parameter.targetProfile. R5 updated the short description, but opd-3 has not changed. OperationDefinition is Normative, so its not clear what is needed to correct opd-3. Also, for IG profiles based on R4, IG Publisher may flag an error if used with a resource for OperationDefinition.parameter.type and using OperationDefinition.parameter.targetProfile.
Attachments
Issue Links
- relates to
-
FHIR-26411 Change OperationDefinition.parameter.targetProfile to also apply to inline resources
- Published
-
FHIR-37969 Need a way to specify when you are using DEQM and base FHIR Operations, you still use DEQM specific profiles
- Published