STU 3 Candidate

This page is part of the FHIR Specification (v1.4.0: STU 3 Ballot 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

CarePlan vs ProcedureRequest

Messages

A series of messages from the comparison algorithm. Errors indicate that solutions cannot be interoperable across both implementation guides (or that there are structural flaws in the definition of at least one).

PathMessage
Errors Detected
CarePlanBase Type is not compatible (CarePlan/ProcedureRequest)
CarePlanisSummary must be the same (false/true)
CarePlanDifferent number of children at CarePlan (24/22)
Notes about differences (e.g. definitions)
CarePlanElements differ in definition for short:
"Healthcare plan for patient or group"
"A request for a procedure to be performed"
CarePlanElements differ in definition for definition:
"Describes the intention of how one or more practitioners intend to deliver care for a particular patient, group or community for a period of time, possibly limited to care for a specific condition or set of conditions."
"A request for a procedure to be performed. May be a proposal or an order."

Intersection

The intersection of the 2 constraint statements. This is what resource authors (either client or server) would need to conform to produce content valid against both implementation guides.

No intersection could be generated

Union

The union of the 2 constraint statements. This is what resource authors (either client or server) would need to be able to handle to accept content valid against either implementation guides.

No union could be generated