-
Type:
Technical Correction
-
Resolution: Persuasive
-
Priority:
Medium
-
FHIR Core (FHIR)
-
R5
-
FHIR Infrastructure
-
Contract
-
Workflow Module
-
-
Correction
-
Yes
-
R5
Contract properly belongs to the Event pattern. The current definition of the Contract resource seems to attempt to track activities related/leading to the Contract activation within the contract itself. This seems to be conflating multiple concept that are in discord with the general Request/Event/Definition patterns.
Suggested changes:
- Move Contract under the Event pattern listing
- Discuss the intent of the Contract resource, and how it can work with other resources like Task to manage the associated life-cycle of the contract.
- relates to
-
FHIR-26966 Contract state machine shows complex workflow that seem to conflate different patterns
-
- Triaged
-