Details
-
Change Request
-
Resolution: Persuasive with Modification
-
Highest
-
FHIR Core (FHIR)
-
R5
-
FHIR Infrastructure
-
STU
-
Appointment
AppointmentResponse
CarePlan
Claim
CommunicationRequest
Contract
CoverageEligibilityRequest
DeviceRequest (was DeviceUseRequest)
EnrollmentRequest
ImmunizationRecommendation
MedicationRequest
NutritionOrder (was NutritionRequest)
RequestOrchestration (was RequestGroup)
ServiceRequest (Diagnostic/Procedure/ReferralRequest)
SupplyRequest
Task
Transport
VisionPrescription
Request Pattern -
-
Bas van den Heuvel/Jose Costa Teixeira: 5-0-0
-
Enhancement
-
Non-substantive
-
R5
Description
Many of the request resources do have fields that correspond the fields indicated in the request pattern and they should.
All fields should be considered.
The fields basedOn, groupIdentifier, intent, requester and subject are critical because main design/interaction patterns in FHIR depend on them.
The field category is very usefull but not present on any of them.
This should be fixed in R5.
Attachments
Issue Links
- is voted on by
-
BALLOT-43367 Negative - Vadim Peretokin : 2022-Sep-FHIR R5 STU
- Withdrawn
-
BALLOT-41610 Negative - Bas van den Heuvel : 2022-Sep-FHIR R5 STU
- Closed
-
BALLOT-42745 Negative - Javier Espina : 2022-Sep-FHIR R5 STU
- Closed
-
BALLOT-42847 Negative - Chris Melo : 2022-Sep-FHIR R5 STU
- Closed
-
BALLOT-42933 Negative - Bert Roos : 2022-Sep-FHIR R5 STU
- Closed
-
BALLOT-43250 Negative - Lisson Zhang : 2022-Sep-FHIR R5 STU
- Closed
-
BALLOT-43807 Negative - David Simons : 2022-Sep-FHIR R5 STU
- Closed
-
BALLOT-43949 Negative - Martin Rosner : 2022-Sep-FHIR R5 STU
- Closed
- relates to
-
FHIR-38871 Event pattern resource should implement the fields from the pattern.
- Published