Details
-
Change Request
-
Resolution: Persuasive
-
Highest
-
FHIR Core (FHIR)
-
R5
-
FHIR Mgmt Group
-
STU
-
(many)
-
-
Josh Mandel/Paul Knapp: 6-0-0
-
Correction
-
Non-compatible
-
R5
Description
The following tickets are resolved but not yet applied. They should applied before R5 is released.
ID | Summary |
Unclear how to deal with information, hybrid and pure computational. All map to RequestGroup? - 2018-May Core STU #15 | |
An example should be added of a Plan Definition that refers to a questionnaire and generates results based on the results. - 2018-May Core STU #28 | |
Needed? Refer to CDS Hooks spec instead. This will allow having two representations of the same spec. - 2018-May Core STU #32 | |
Why would we want to? Trigger Definition is needed. - 2018-May Core STU #34 | |
Add element on measure resource related to Meaningful Measures domain (https://www.cms.gov/Medicare/Quality-Initiatives-Patient-Assessment-Instruments/QualityInitiativesGenInfo/MMF/General-info-Sub-Page.html) as defined by CMS - 2018-May Core STU #42 | |
StructureMap $transform does not allow passing of StructureMap resource | |
Clarify language around invoking multiple groups | |
Clarify behaviour for matching multiple source statements | |
RequestGroup does not allow searching on based-on | |
Missing value set for Device.property.type | |
Missing value set for DeviceDefinition.property.type | |
Clinical reasoning cannot generate event resources | |
ActitivityDefinition does not specify the transform to generate resources | |
Expressions must be able access parameter fields. | |
CapabilityStatement state support of async | |
How to use a Activity/PlanDefinition to update an existing resource | |
How to store parameters of a procedure in ServiceRequest in a structure way? | |
Missing value set for Device.property.type | |
Missing value set for DeviceDefinition.property.type | |
Slots should provide eligibility/constraints parameters | |
There are few elements with types: CodeableConcept and code without linked value set and binding specified | |
Expand SampledData to allow for variable timings | |
How to represent a device to be used (e.g., for administration of a medication) in ActivityDefinition? | |
Clarification about MedicationAdministration.performer | |
Spelling error: ObesrvationDefinitions instead of ObservationDefinitions |
Attachments
Issue Links
- is voted on by
-
BALLOT-43329 Negative - Vadim Peretokin : 2022-Sep-FHIR R5 STU
- Withdrawn
-
BALLOT-41893 Negative - Bas van den Heuvel : 2022-Sep-FHIR R5 STU
- Closed
-
BALLOT-42707 Negative - Javier Espina : 2022-Sep-FHIR R5 STU
- Closed
-
BALLOT-42809 Negative - Chris Melo : 2022-Sep-FHIR R5 STU
- Closed
-
BALLOT-42895 Negative - Bert Roos : 2022-Sep-FHIR R5 STU
- Closed
-
BALLOT-43212 Negative - Lisson Zhang : 2022-Sep-FHIR R5 STU
- Closed
-
BALLOT-43769 Negative - David Simons : 2022-Sep-FHIR R5 STU
- Closed
-
BALLOT-43911 Negative - Martin Rosner : 2022-Sep-FHIR R5 STU
- Closed