Current Build

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

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

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

Communication
Element IdCommunication
Definition

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

Control0..*
TypeDomainResource
Communication.identifier
Element IdCommunication.identifier
Definition

Business identifiers assigned to this communication 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 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.

Communication.instantiatesCanonical
Element IdCommunication.instantiatesCanonical
Definition

The URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this Communication.

Control0..*
Typecanonical(PlanDefinition | ActivityDefinition | Measure | OperationDefinition | Questionnaire)
Summarytrue
Communication.instantiatesUri
Element IdCommunication.instantiatesUri
Definition

The URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this Communication.

Control0..*
Typeuri
Summarytrue
Comments

This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.

Communication.basedOn
Element IdCommunication.basedOn
Definition

An order, proposal or plan fulfilled in whole or in part by this Communication.

Control0..*
TypeReference(Any)
Alternate Namesfulfills
Summarytrue
Comments

This must point to some sort of a 'Request' resource, such as CarePlan, CommunicationRequest, ServiceRequest, MedicationRequest, etc.

Communication.partOf
Element IdCommunication.partOf
Definition

Part of this action.

Control0..*
TypeReference(Any)
Alternate Namescontainer
Summarytrue
Communication.inResponseTo
Element IdCommunication.inResponseTo
Definition

Prior communication that this communication is in response to.

Control0..*
TypeReference(Communication)
Communication.status
Element IdCommunication.status
Definition

Статус передачи.

Control1..1
Terminology BindingEventStatus (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
Comments

This element is labeled as a modifier because the status contains the codes aborted and entered-in-error that mark the communication as not currently valid.

Communication.statusReason
Element IdCommunication.statusReason
Definition

Captures the reason for the current state of the Communication.

Control0..1
Terminology BindingCommunicationNotDoneReason (Example)
TypeCodeableConcept
Alternate NamesSuspended Reason; Cancelled Reason
Summarytrue
Comments

This is generally only used for "exception" statuses such as "not-done", "suspended" or "aborted". The reason for performing the event at all is captured in reasonCode, not here.

Communication.category
Element IdCommunication.category
Definition

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

Control0..*
Terminology BindingCommunicationCategory (Example)
TypeCodeableConcept
Comments

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

Communication.priority
Element IdCommunication.priority
Definition

Characterizes how quickly the planned or in progress communication must be addressed. Includes concepts such as stat, urgent, routine.

Control0..1
Terminology BindingRequest priority (Required)
Typecode
Meaning if MissingIf missing, this communication should be treated with normal priority
Summarytrue
Comments

Used to prioritize workflow (such as which communication to read first) when the communication is planned or in progress.

Communication.medium
Element IdCommunication.medium
Definition

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

Control0..*
Terminology Bindingv3 Code System ParticipationMode (Example)
TypeCodeableConcept
Communication.subject
Element IdCommunication.subject
Definition

The patient or group that was the focus of this communication.

Control0..1
TypeReference(Patient | Group)
Alternate Namespatient
Summarytrue
Communication.topic
Element IdCommunication.topic
Definition

Description of the purpose/content, similar to a subject line in an email.

Control0..1
Terminology BindingCommunicationTopic (Example)
TypeCodeableConcept
Comments

Communication.topic.text can be used without any codings.

Communication.about
Element IdCommunication.about
Definition

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

Control0..*
TypeReference(Any)
Comments

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

Communication.encounter
Element IdCommunication.encounter
Definition

The Encounter during which this Communication 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.

Communication.sent
Element IdCommunication.sent
Definition

Время, когда это сообщение было отправлено.

Control0..1
TypedateTime
Communication.received
Element IdCommunication.received
Definition

Время, когда это сообщение прибыло в пункт назначения.

Control0..1
TypedateTime
Communication.recipient
Element IdCommunication.recipient
Definition

The entity (e.g. person, organization, clinical information system, care team or device) which was the target of the communication. If receipts need to be tracked by individual, a separate resource instance will need to be created for each recipient. Multiple recipient communications are intended where either a receipt(s) is not tracked (e.g. a mass mail-out) or is captured in aggregate (all emails confirmed received by a particular time).

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

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

Control0..1
TypeReference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson | HealthcareService)
Communication.reasonCode
Element IdCommunication.reasonCode
Definition

Причина или обоснование этой коммуникации.

Control0..*
Terminology BindingSNOMED CT Clinical Findings (Example)
TypeCodeableConcept
Summarytrue
Comments

Textual reasons can be captured using reasonCode.text.

Communication.reasonReference
Element IdCommunication.reasonReference
Definition

Indicates another resource whose existence justifies this communication.

Control0..*
TypeReference(Condition | Observation | DiagnosticReport | DocumentReference)
Summarytrue
Communication.payload
Element IdCommunication.payload
Definition

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

Control0..*
Communication.payload.content[x]
Element IdCommunication.payload.content[x]
Definition

A 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]
Communication.note
Element IdCommunication.note
Definition

Additional notes or commentary about the communication by the sender, receiver or other interested parties.

Control0..*
TypeAnnotation