-
-
Key: = Must support, = QICore-defined extension, = Is-Modifier
Field Card. Type and Description 
authoredOn 0..1DateTimeDate/DateTime of creation for draft requests and date of activation for active requests.basedOn 0..*List<Reference>Indicates any plans, proposals or orders that this request is intended to satisfy - in whole or in part.context 0..1ReferenceThe encounter at which the request for referral or transfer of care is initiated.definition 0..*List<Reference>A protocol, guideline, orderset or other definition that is adhered to in whole or in part by this request.description 0..1StringThe reason element gives a short description of why the referral is being made, the description expands on this to support a more complete clinical summary.groupIdentifier 0..1IdentifierThe business identifier of the logical "grouping" request/order that this referral is a part of.identifier 0..*List<Identifier>Business identifier that uniquely identifies the referral/care transfer request instance.intent 1..1StringDistinguishes the "level" of authorization/demand implicit in this request.Binding: RequestIntent (Required)
note 0..*List<Annotation>Comments made about the referral request by any of the participants.occurrence[x] 0..1Interval<DateTime | Interval<DateTime>The period of time within which the services identified in the referral/transfer of care is specified or required to occur.priority 0..1StringAn indication of the urgency of referral (or where applicable the type of transfer of care) request.Binding: RequestPriority (Required)
reasonCode 0..*List<Concept>Description of clinical condition indicating why referral/transfer of care is requested. For example: Pathological Anomalies, Disabled (physical or mental), Behavioral Management.Binding: SNOMED CT Clinical Findings (Example)
reasonReference 0..*List<Reference>Indicates another resource whose existence justifies this request.recipient 0..*List<Reference>The healthcare provider(s) or provider organization(s) who/which is to receive the referral/transfer of care request.refusalReason 0..1ExtensionAn ExtensionrelevantHistory 0..*List<Reference>Links to Provenance records for past versions of this resource or fulfilling request or event resources that identify key state transitions or updates that are likely to be relevant to a user looking at the current version of the resource.replaces 0..*List<Reference>Completed or terminated request(s) whose function is taken by this new request.requester 0..1RequesterThe individual who initiated the request and has responsibility for its activation.serviceRequested 0..*List<Concept>The service(s) that is/are requested to be provided to the patient. For example: cardiac pacemaker insertion.Binding: Practice Setting Code Value Set (Example)
specialty 0..1ConceptIndication of the clinical domain or discipline to which the referral or transfer of care request is sent. For example: Cardiology Gastroenterology Diabetology.Binding: PractitionerSpecialty (Example)
status 1..1StringThe status of the authorization/intention reflected by the referral request record.Binding: RequestStatus (Required)
subject 1..1ReferenceThe patient who is the subject of a referral or transfer of care request.supportingInfo 0..*List<Reference>Any additional (administrative, financial or clinical) information required to support request for referral or transfer of care. For example: Presenting problems/chief complaints Medical History Family History Alerts Allergy/Intolerance and Adverse Reactions Medications Observations/Assessments (may include cognitive and fundtional assessments) Diagnostic Reports Care Plan.type 0..1ConceptAn indication of the type of referral (or where applicable the type of transfer of care) request.(Example)
Key: = Must support, = QICore-defined extension, = Is-Modifier
-