Nachrichten (Communication)
Ärzte können Patienten erlauben ihnen über das ESYSTA-Portal Nachrichten zu senden, auf die Ärzte wiederum antworten können. So entsteht ein sicheres Kommunikationsmedium zwischen Patienten und Ärzten. Die folgende Festlegung beschreibt Nachrichten (EsystaCommunication) im ESYSTA-Portal. Ein Nachrichtenaustausch (sender und recepient) findet stets zwischen einem Patienten (DiabetesPatient) und einem Arzt (Practitioner) statt, enthält einen Inhalt (payload) und einen Betreff (topic).
Kompatibilität
Dieses Profil basiert auf der Basisdefinition des FHIR Communication und wurde durch Einschränkungen spezifiziert. Instanzen müssen gegen das folgende FHIR-Profil valide sein.
FHIR-Profil (EsystaCommunication)
| EsystaCommunication (Communication) | C | Communication | There are no (further) constraints on this element Element idCommunicationShort description A record of information transmitted from a sender to a receiver DefinitionAn occurrence of information being transmitted; e.g. an alert that was sent to a responsible provider, a public health agency that was notified about a reportable condition.
| |||
| id | Σ | 0..1 | string | There are no (further) constraints on this element Element idCommunication.idShort description Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. | ||
| meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idCommunication.metaShort description Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idCommunication.implicitRulesShort description A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| language | 0..1 | codeBinding | There are no (further) constraints on this element Element idCommunication.languageShort description Language of the resource content DefinitionThe base language in which the resource is written. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). A human language.
The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| text | 0..1 | Narrative | There are no (further) constraints on this element Element idCommunication.textShort description Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| contained | 0..* | Resource | There are no (further) constraints on this element Element idCommunication.containedShort description Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
| |||
| extension | S C | 0..1 | Extension | Element idCommunication.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| messageRead | C | 0..1 | Extension(boolean) | Element idCommunication.extension:messageReadShort description Optional Extensions Element Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. http://portal.esysta.com/fhir/StructureDefinition/MessageRead ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| modifierExtension | ?! C | 0..* | Extension | There are no (further) constraints on this element Element idCommunication.modifierExtensionShort description Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| identifier | S Σ | 1..1 | Identifier | There are no (further) constraints on this element Element idCommunication.identifierShort description Unique identifier DefinitionBusiness 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. Allows identification of the communication as it is known by various participating systems and in a way that remains consistent across servers. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| instantiatesCanonical | Σ | 0..* | canonical(ActivityDefinition | Measure | OperationDefinition | PlanDefinition | Questionnaire) | There are no (further) constraints on this element Element idCommunication.instantiatesCanonicalShort description Instantiates FHIR protocol or definition DefinitionThe URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this Communication. canonical(ActivityDefinition | Measure | OperationDefinition | PlanDefinition | Questionnaire) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| instantiatesUri | Σ | 0..* | uri | There are no (further) constraints on this element Element idCommunication.instantiatesUriShort description Instantiates external protocol or definition DefinitionThe URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this Communication. This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| basedOn | Σ C | 0..* | Reference(Resource) | There are no (further) constraints on this element Element idCommunication.basedOnShort description Request fulfilled by this communication Alternate namesfulfills DefinitionAn order, proposal or plan fulfilled in whole or in part by this Communication. This must point to some sort of a 'Request' resource, such as CarePlan, CommunicationRequest, ServiceRequest, MedicationRequest, etc. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| partOf | Σ C | 0..* | Reference(Resource) | There are no (further) constraints on this element Element idCommunication.partOfShort description Part of this action Alternate namescontainer DefinitionPart of this action. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| inResponseTo | C | 0..* | Reference(Communication) | There are no (further) constraints on this element Element idCommunication.inResponseToShort description Reply to DefinitionPrior communication that this communication is in response to. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| status | Σ ?! | 1..1 | codeBinding | There are no (further) constraints on this element Element idCommunication.statusShort description preparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown DefinitionThe status of the transmission. 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. The status of the communication. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| statusReason | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idCommunication.statusReasonShort description Reason for current status Alternate namesSuspended Reason, Cancelled Reason DefinitionCaptures the reason for the current state of the Communication. 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. Codes for the reason why a communication did not happen. CommunicationNotDoneReason (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| category | 0..* | CodeableConcept | There are no (further) constraints on this element Element idCommunication.categoryShort description Message category DefinitionThe type of message conveyed such as alert, notification, reminder, instruction, etc. There may be multiple axes of categorization and one communication may serve multiple purposes. Codes for general categories of communications such as alerts, instructions, etc. CommunicationCategory (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| priority | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element idCommunication.priorityShort description routine | urgent | asap | stat DefinitionCharacterizes how quickly the planned or in progress communication must be addressed. Includes concepts such as stat, urgent, routine. Used to prioritize workflow (such as which communication to read first) when the communication is planned or in progress. If missing, this communication should be treated with normal priority Codes indicating the relative importance of a communication. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| medium | 0..* | CodeableConcept | There are no (further) constraints on this element Element idCommunication.mediumShort description A channel of communication DefinitionA channel that was used for this communication (e.g. email, fax). 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. Codes for communication mediums such as phone, fax, email, in person, etc. v3.ParticipationMode (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| subject | Σ C | 0..1 | Reference(Group | Patient) | There are no (further) constraints on this element Element idCommunication.subjectShort description Focus of message Alternate namespatient DefinitionThe patient or group that was the focus of this communication. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| topic | S | 1..1 | CodeableConcept | There are no (further) constraints on this element Element idCommunication.topicShort description Description of the purpose/content DefinitionDescription of the purpose/content, similar to a subject line in an email. Communication.topic.text can be used without any codings. Codes describing the purpose or content of the communication. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| about | C | 0..* | Reference(Resource) | There are no (further) constraints on this element Element idCommunication.aboutShort description Resources that pertain to this communication DefinitionOther resources that pertain to this communication and to which this communication should be associated. Don't use Communication.about element when a more specific element exists, such as basedOn or reasonReference. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| encounter | Σ C | 0..1 | Reference(Encounter) | There are no (further) constraints on this element Element idCommunication.encounterShort description Encounter created as part of DefinitionThe Encounter during which this Communication was created or to which the creation of this record is tightly associated. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| sent | S | 1..1 | dateTime | There are no (further) constraints on this element Element idCommunication.sentShort description When sent DefinitionThe time when this communication was sent. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| received | 0..1 | dateTime | There are no (further) constraints on this element Element idCommunication.receivedShort description When received DefinitionThe time when this communication arrived at the destination. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| recipient | S C | 1..1 | Reference(DiabetesPatient | Practitioner) | Element idCommunication.recipientShort description Message recipient DefinitionThe 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 an individual, a separate resource instance will need to be created for each recipient. Multiple recipient communications are intended where either receipts are not tracked (e.g. a mass mail-out) or a receipt is captured in aggregate (all emails confirmed received by a particular time). 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(DiabetesPatient | Practitioner) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| sender | S C | 1..1 | Reference(DiabetesPatient | Practitioner) | Element idCommunication.senderShort description Message sender DefinitionThe entity (e.g. person, organization, clinical information system, or device) which was the source of the communication. 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(DiabetesPatient | Practitioner) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| reasonCode | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element idCommunication.reasonCodeShort description Indication for message DefinitionThe reason or justification for the communication. Textual reasons can be captured using reasonCode.text. Codes for describing reasons for the occurrence of a communication. SNOMEDCTClinicalFindings (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| reasonReference | Σ C | 0..* | Reference(Condition | DiagnosticReport | DocumentReference | Observation) | There are no (further) constraints on this element Element idCommunication.reasonReferenceShort description Why was communication done? DefinitionIndicates another resource whose existence justifies this communication. 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 | DiagnosticReport | DocumentReference | Observation) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| payload | S | 1..1 | BackboneElement | There are no (further) constraints on this element Element idCommunication.payloadShort description Message payload DefinitionText, attachment(s), or resource(s) that was communicated to the recipient. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idCommunication.payload.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idCommunication.payload.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idCommunication.payload.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| content[x] | 1..1 | There are no (further) constraints on this element Element idCommunication.payload.content[x]Short description Message part content DefinitionA communicated content (or for multi-part communications, one portion of the communication). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||
| contentAttachment | Attachment | There are no (further) constraints on this element Data type | ||||
| contentReference | Reference(Resource) | There are no (further) constraints on this element Data type | ||||
| contentString | string | There are no (further) constraints on this element Data type | ||||
| note | 0..* | Annotation | There are no (further) constraints on this element Element idCommunication.noteShort description Comments made about the communication DefinitionAdditional notes or commentary about the communication by the sender, receiver or other interested parties. 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
|
Beispiel
Fiktives Beispiel einer validen EsystaCommunication Instanz: