CBR Verwijzing
Het CBR Verwijzing profiel wordt gebruikt voor de ReferralRequest resource die door het CBR naar ZorgDomein verzonden wordt om de details van een keuring door te geven. Deze resource wordt meegestuurd in de Bundle met de Composition conform CBR Document. Deze Bundle wordt door het CBR naar ZorgDomein verstuurd om een keuring aan te melden.
De canonical URL van dit profiel is:
http://zorgdomein.nl/fhir/StructureDefinition/cbr-verwijzing
Dit profiel is afgeleid van de ReferralRequest resource.
| ReferralRequest | 0..* | ReferralRequest | Element Id
ReferralRequest CBR Verwijzing Alternate namesReferralRequest TransferOfCare Request DefinitionUsed 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.
|
|
| identifier | Σ | 1..1 | Identifier | Element Id
ReferralRequest.identifier Business identifier DefinitionBusiness identifier that uniquely identifies the referral/care transfer request instance.
|
| use | Σ ?! | 0..1 | codeBinding | Element Id
ReferralRequest.identifier.use usual | official | temp | secondary (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. This is labeled as "Is Modifier" because applications should not mistake a temporary id for a permanent one. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.
|
| type | Σ | 0..1 | CodeableConceptBinding | Element Id
ReferralRequest.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
|
| system | Σ | 1..1 | uriFixed Value | Element Id
ReferralRequest.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. see http://en.wikipedia.org/wiki/Uniform_resource_identifier
http://cbr.nl/
|
| value | Σ | 1..1 | string | Element Id
ReferralRequest.identifier.value CBR_VERWIJZING_ID: Door het CBR toegekende unieke ID voor de verwijzing DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension.
General
123456 Mappings
|
| period | Σ | 0..1 | Period | Element Id
ReferralRequest.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. This is not a duration - that's a measure of time (a separate type), but a duration that occurs at a fixed value of time. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). If duration is required, specify the type as Interval|Duration.
|
| assigner | Σ | 0..1 | Reference(Organization) | Element Id
ReferralRequest.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
|
| definition | Σ | 0..* | Reference(ActivityDefinition | PlanDefinition) | Element Id
ReferralRequest.definition Instantiates protocol or definition DefinitionA protocol, guideline, orderset or other definition that is adhered to in whole or in part by this request. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(ActivityDefinition | PlanDefinition) Constraints
|
| basedOn | Σ | 0..* | Reference(ReferralRequest | CarePlan | ProcedureRequest) | Element Id
ReferralRequest.basedOn Request fulfilled by this request Alternate namesfulfills DefinitionIndicates any plans, proposals or orders that this request is intended to satisfy - in whole or in part. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(ReferralRequest | CarePlan | ProcedureRequest) Constraints
|
| replaces | Σ | 0..* | Reference(ReferralRequest) | Element Id
ReferralRequest.replaces Request(s) replaced by this request Alternate namessupersedes, prior, renewed order DefinitionCompleted or terminated request(s) whose function is taken by this new request. Allows tracing the continuation of a therapy or administrative process instantiated through multiple requests. The replacement could be because the initial request was immediately rejected (due to an issue) or because the previous request was completed, but the need for the action described by the request remains ongoing.
|
| groupIdentifier | Σ | 0..1 | Identifier | Element Id
ReferralRequest.groupIdentifier Composite request this is part of Alternate namesgrouperId, requisition DefinitionThe business identifier of the logical "grouping" request/order that this referral is a part of. Allows multiple orders to be collected as part of a single requisition.
|
| status | Σ ?! | 1..1 | codeBindingFixed Value | Element Id
ReferralRequest.status STATUS: Voor een verwijzing heeft dit veld de waarde "active" DefinitionThe status of the authorization/intention reflected by the referral request record. Workflow status is handled by the Task resource. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.
active
|
| intent | Σ ?! | 1..1 | codeBindingFixed Value | Element Id
ReferralRequest.intent CATEGORY: Voor een verwijzing heeft dit veld de waarde "order" Alternate namescategory DefinitionDistinguishes the "level" of authorization/demand implicit in this request. The same resource structure is used when capturing proposals/recommendations, plans and actual requests. Note that FHIR strings may not exceed 1MB in size
order
|
| type | Σ | 0..1 | CodeableConcept | Element Id
ReferralRequest.type Referral/Transition of care request type DefinitionAn indication of the type of referral (or where applicable the type of transfer of care) request. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
|
| priority | Σ | 0..1 | codeBinding | Element Id
ReferralRequest.priority Urgency of referral / transfer of care request DefinitionAn indication of the urgency of referral (or where applicable the type of transfer of care) request. Note that FHIR strings may not exceed 1MB in size
|
| serviceRequested | Σ | 0..* | CodeableConcept | Element Id
ReferralRequest.serviceRequested Actions requested as part of the referral DefinitionThe service(s) that is/are requested to be provided to the patient. For example: cardiac pacemaker insertion. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
|
| subject | Σ | 1..1 | Reference(http://zorgdomein.nl/fhir/StructureDefinition/zd-patient) | Element Id
ReferralRequest.subject BURGER_CODE: Afleiden uit referentie naar CBR Burger DefinitionThe patient who is the subject of a referral or transfer of care request. Referral of family, group or community is to be catered for by profiles. Reference(http://zorgdomein.nl/fhir/StructureDefinition/zd-patient) Constraints
|
| context | Σ | 0..1 | Reference(Encounter | EpisodeOfCare) | Element Id
ReferralRequest.context Originating encounter Alternate namesencounter DefinitionThe encounter at which the request for referral or transfer of care is initiated. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Encounter | EpisodeOfCare) Constraints
|
| occurrence[x] | Σ | 0..1 | Element Id
ReferralRequest.occurrence[x] When the service(s) requested in the referral should occur Alternate namestiming DefinitionThe period of time within which the services identified in the referral/transfer of care is specified or required to occur. Use cases: (1) to indicate that the requested service is not to happen before a specified date, and saving the start date in Period.start; (2) to indicate that the requested service must happen before a specified date, and saving the end date in Period.end; (3) to indicate that the requested service must happen during the specified dates ("start" and "end" values). When the occurrenceDateTime is used, then it is indicating that the requested service must happen before the specified date.
|
|
| occurrenceDateTime | dateTime | Data Type | ||
| occurrencePeriod | Period | Data Type | ||
| authoredOn | Σ | 0..1 | dateTime | Element Id
ReferralRequest.authoredOn Date of creation/activation Alternate namescreatedOn DefinitionDate/DateTime of creation for draft requests and date of activation for active requests.
|
| requester | Σ | 0..1 | BackboneElement | Element Id
ReferralRequest.requester Who/what is requesting service Alternate namesauthor DefinitionThe individual who initiated the request and has responsibility for its activation.
|
| agent | Σ | 1..1 | Reference(Practitioner | Organization | Patient | RelatedPerson | Device) | Element Id
ReferralRequest.requester.agent Individual making the request DefinitionThe device, practitioner, etc. who initiated the request. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Practitioner | Organization | Patient | RelatedPerson | Device) Constraints
|
| onBehalfOf | Σ | 0..1 | Reference(Organization) | Element Id
ReferralRequest.requester.onBehalfOf Organization agent is acting for DefinitionThe organization the device or practitioner was acting on behalf of. Practitioners and Devices can be associated with multiple organizations. This element indicates which organization they were acting on behalf of when authoring the request. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
| specialty | 0..1 | CodeableConcept | Element Id
ReferralRequest.specialty The clinical specialty (discipline) that the referral is requested for DefinitionIndication of the clinical domain or discipline to which the referral or transfer of care request is sent. For example: Cardiology Gastroenterology Diabetology. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. practitioner-specialty (example) Constraints
|
|
| recipient | Σ | 0..* | Reference(Practitioner | Organization | HealthcareService) | Element Id
ReferralRequest.recipient Receiver of referral / transfer of care request DefinitionThe healthcare provider(s) or provider organization(s) who/which is to receive the referral/transfer of care request. There will be a primary receiver. But the request can be received by any number of "copied to" providers or organizations. Reference(Practitioner | Organization | HealthcareService) Constraints
|
| reasonCode | Σ | 1..1 | CodeableConcept | Element Id
ReferralRequest.reasonCode Reason for referral / transfer of care request DefinitionDescription of clinical condition indicating why referral/transfer of care is requested. For example: Pathological Anomalies, Disabled (physical or mental), Behavioral Management. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
|
| coding | Σ | 1..1 | Coding | Element Id
ReferralRequest.reasonCode.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
| system | Σ | 0..1 | uri | Element Id
ReferralRequest.reasonCode.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously.
|
| version | Σ | 0..1 | string | Element Id
ReferralRequest.reasonCode.coding.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
| code | Σ | 1..1 | code | Element Id
ReferralRequest.reasonCode.coding.code ZD_ZORGVRAAGCODE: Door ZorgDomein toegekende unieke code voor de zorgvraag. VB: "NEUEPI" = "Neurologie Epilepsie" DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
|
| display | Σ | 0..1 | string | Element Id
ReferralRequest.reasonCode.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
|
| userSelected | Σ | 0..1 | boolean | Element Id
ReferralRequest.reasonCode.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
| text | Σ | 0..1 | string | Element Id
ReferralRequest.reasonCode.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
| reasonReference | Σ | 0..* | Reference(Condition | Observation) | Element Id
ReferralRequest.reasonReference Why is service needed? DefinitionIndicates another resource whose existence justifies this request. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Condition | Observation) Constraints
|
| description | 0..1 | string | Element Id
ReferralRequest.description A textual description of the referral DefinitionThe 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. Note that FHIR strings may not exceed 1MB in size
|
|
| supportingInfo | 0..* | Reference(Resource) | Element Id
ReferralRequest.supportingInfo Additonal information to support referral or transfer of care request DefinitionAny 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. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
|
| note | 0..* | Annotation | Element Id
ReferralRequest.note Comments made about referral request DefinitionComments made about the referral request by any of the participants. For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).
|
|
| relevantHistory | 0..* | Reference(Provenance) | Element Id
ReferralRequest.relevantHistory Key events in history of request Alternate nameseventHistory DefinitionLinks 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. This element does not point to the Provenance associated with the current version of the resource - as it would be created after this version existed. The Provenance for the current version can be retrieved with a _revinclude.
|