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

ProcedureRequest vs ReferralRequest

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
ProcedureRequestBase Type is not compatible (ProcedureRequest/ReferralRequest)
ProcedureRequestisSummary must be the same (true/false)
ProcedureRequestDifferent number of children at ProcedureRequest (22/26)
Notes about differences (e.g. definitions)
ProcedureRequestElements differ in definition for short:
"A request for a procedure to be performed"
"A request for referral or transfer of care"
ProcedureRequestElements differ in definition for definition:
"A request for a procedure to be performed. May be a proposal or an order."
"Used to record and send details about a request for referral service or transfer of a patient to the care of another provider or provider organization."

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