Current Build

Переводит команда Health Samurai . Приглашаем поучаствовать в русификации стандарта FHIR: GitHub , Email.

Patient Care Work GroupMaturity Level: 2 Trial Use Compartments: Device, Encounter, Patient, Practitioner, RelatedPerson

Подробное описание элементов ресурса CommunicationRequest.

CommunicationRequest
Element IdCommunicationRequest
Definition

Запрос на передачу информации; например система поддержки принятия решений предлагает отправить оповещение ответственному врачу; система поддержки принятия решений предлагает оповестить организацию общественного здравоохранения о подлежащем регистрации состоянии.

Control0..*
TypeDomainResource
CommunicationRequest.identifier
Element IdCommunicationRequest.identifier
Definition

Business identifiers assigned to this communication request by the performer or other systems which remain constant as the resource is updated and propagates from server to server.

NoteThis is a business identifer, not a resource identifier (see discussion)
Control0..*
TypeIdentifier
Requirements

Allows identification of the communication request as it is known by various participating systems and in a way that remains consistent across servers.

Summarytrue
Comments

This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.

CommunicationRequest.basedOn
Element IdCommunicationRequest.basedOn
Definition

A plan or proposal that is fulfilled in whole or in part by this request.

Control0..*
TypeReference(Any)
Requirements

Allows tracing of authorization for the request and tracking whether proposals/recommendations were acted upon.

Alternate Namesfulfills
Summarytrue
CommunicationRequest.replaces
Element IdCommunicationRequest.replaces
Definition

Completed or terminated request(s) whose function is taken by this new request.

Control0..*
TypeReference(CommunicationRequest)
Requirements

Allows tracing the continuation of a therapy or administrative process instantiated through multiple requests.

Alternate Namessupersedes; prior
Summarytrue
Comments

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.

CommunicationRequest.groupIdentifier
Element IdCommunicationRequest.groupIdentifier
Definition

A shared identifier common to all requests that were authorized more or less simultaneously by a single author, representing the identifier of the requisition, prescription or similar form.

Control0..1
TypeIdentifier
Alternate NamesgrouperId
Summarytrue
Comments

Requests are linked either by a "basedOn" relationship (i.e. one request is fulfilling another) or by having a common requisition. Requests that are part of the same requisition are generally treated independently from the perspective of changing their state or maintaining them after initial creation.

CommunicationRequest.status
Element IdCommunicationRequest.status
Definition

Статус предложения или заказа.

Control1..1
Terminology BindingRequestStatus (Required)
Typecode
Is Modifiertrue (Reason: This element is labelled as a modifier because it is a status element that contains status entered-in-error which means that the resource should not be treated as valid.)
Summarytrue
CommunicationRequest.statusReason
Element IdCommunicationRequest.statusReason
Definition

Captures the reason for the current state of the CommunicationRequest.

Control0..1
Terminology BindingCommunicationRequestStatusReason:
TypeCodeableConcept
Alternate NamesSuspended Reason; Cancelled Reason
Comments

This is generally only used for "exception" statuses such as "suspended" or "cancelled". The reason why the CommunicationRequest was created at all is captured in reasonCode, not here. [distinct reason codes for different statuses can be enforced using invariants if they are universal bindings].

CommunicationRequest.category
Element IdCommunicationRequest.category
Definition

Тип передаваемого сообщения, например предупреждение, уведомление, напоминание, инструкция и т. д.

Control0..*
Terminology BindingCommunicationCategory (Example)
TypeCodeableConcept
Comments

There may be multiple axes of categorization and one communication request may serve multiple purposes.

CommunicationRequest.priority
Element IdCommunicationRequest.priority
Definition

Характеризует, насколько быстро предложенное действие должно быть инициировано. Включает в себя такие понятия, как немедленно, срочно, обычная срочность.

Control0..1
Terminology BindingRequest priority (Required)
Typecode
Meaning if MissingIf missing, this task should be performed with normal priority
Summarytrue
CommunicationRequest.doNotPerform
Element IdCommunicationRequest.doNotPerform
Definition

If true indicates that the CommunicationRequest is asking for the specified action to not occur.

Control0..1
Typeboolean
Is Modifiertrue (Reason: If true this element negates the specified action. For Example, instead of a request for a communication, it is a request for the communication to not occur.)
Meaning if MissingIf do not perform is not specified, the request is a positive request e.g. "do perform"
Alternate Namesprohibited
Summarytrue
Comments

The attributes provided with the request qualify what is not to be done.

CommunicationRequest.medium
Element IdCommunicationRequest.medium
Definition

Канал, который использовался для данной коммуникации (например электронная почта, факс).

Control0..*
Terminology Bindingv3 Code System ParticipationMode (Example)
TypeCodeableConcept
CommunicationRequest.subject
Element IdCommunicationRequest.subject
Definition

The patient or group that is the focus of this communication request.

Control0..1
TypeReference(Patient | Group)
Alternate Namespatient
CommunicationRequest.about
Element IdCommunicationRequest.about
Definition

Other resources that pertain to this communication request and to which this communication request should be associated.

Control0..*
TypeReference(Any)
Comments

Don't use CommunicationRequest.about element when a more specific element exists, such as basedOn, reasonReference, or replaces.

CommunicationRequest.encounter
Element IdCommunicationRequest.encounter
Definition

The Encounter during which this CommunicationRequest was created or to which the creation of this record is tightly associated.

Control0..1
TypeReference(Encounter)
Summarytrue
Comments

This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter.

CommunicationRequest.payload
Element IdCommunicationRequest.payload
Definition

Текст, вложения или ресурсы, которые были сообщены получателю.

Control0..*
CommunicationRequest.payload.content[x]
Element IdCommunicationRequest.payload.content[x]
Definition

The communicated content (or for multi-part communications, one portion of the communication).

Control1..1
Typestring|Attachment|Reference(Any)
[x] NoteSee Choice of Data Types for further information about how to use [x]
CommunicationRequest.occurrence[x]
Element IdCommunicationRequest.occurrence[x]
Definition

Время, когда должна произойти эта коммуникация.

Control0..1
TypedateTime|Period
[x] NoteSee Choice of Data Types for further information about how to use [x]
Alternate Namestiming
Summarytrue
CommunicationRequest.authoredOn
Element IdCommunicationRequest.authoredOn
Definition

For draft requests, indicates the date of initial creation. For requests with other statuses, indicates the date of activation.

Control0..1
TypedateTime
Alternate NamescreatedOn
Summarytrue
CommunicationRequest.requester
Element IdCommunicationRequest.requester
Definition

The device, individual, or organization who initiated the request and has responsibility for its activation.

Control0..1
TypeReference(Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device)
Alternate Namesauthor
Summarytrue
CommunicationRequest.recipient
Element IdCommunicationRequest.recipient
Definition

Сущность (например человек, организация, клиническая информационная система, или устройство), которая была целью коммуникации.

Control0..*
TypeReference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson | Group | CareTeam | HealthcareService)
CommunicationRequest.sender
Element IdCommunicationRequest.sender
Definition

Сущность (например человек, организация, клиническая информационная система, или устройство), которая была источником коммуникации.

Control0..1
TypeReference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson | HealthcareService)
Summarytrue
CommunicationRequest.reasonCode
Element IdCommunicationRequest.reasonCode
Definition

Describes why the request is being made in coded or textual form.

Control0..*
Terminology Bindingv3 Code System ActReason (Example)
TypeCodeableConcept
Summarytrue
Comments

Textual reasons can be captured using reasonCode.text.

CommunicationRequest.reasonReference
Element IdCommunicationRequest.reasonReference
Definition

Indicates another resource whose existence justifies this request.

Control0..*
TypeReference(Condition | Observation | DiagnosticReport | DocumentReference)
Summarytrue
CommunicationRequest.note
Element IdCommunicationRequest.note
Definition

Comments made about the request by the requester, sender, recipient, subject or other participants.

Control0..*
TypeAnnotation