StructureDefinition-be-communication

Sourceehealthplatform.be.r4.federalprofiles#1.3.3-beta:eHealth Platform R4 Federal Profiles (v4.0.1)
resourceTypeStructureDefinition
idbe-communication
canonicalhttps://www.ehealth.fgov.be/standards/fhir/StructureDefinition/be-communication
version1.0.0
statusactive
publishereHealth Platform
nameBeCommunication
titleBeCommunication
date2021-01-18T09:02:46+00:00
descriptionThis is the technical specification for the Communication resource, as it is used in Belgium. This specification is compatible with the current version of KMEHR Diary Note, namely the selection of attributes that are supported, and the maximum length of the payload (320 characters). It also relies on the foundation Belgium resources, for example the Belgian Patient, Practitioner and other resources.
fhirVersion4.0.1
kindresource
abstractfalse
sdTtypeCommunication
derivationconstraint
basehttp://hl7.org/fhir/StructureDefinition/Communication
Usages(none)
Name Flags Card. Type Description & Constraints doco
. . Communication Communication
. . . identifier S Unique identifier for this communication
. . . status S Status of this communication: preparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown
. . . category S
. . . priority S
. . . subject S Reference (BePatient | Group ) Subject of the communication - typically Patient
. . . topic S Topic of the communication
Binding: BeVSDiaryTopic ( preferred )
. . . sent S Date and Time that the communication has been sent
. . . recipient S Reference ( Device | BePatient | BePractitioner | BePractitionerRole | RelatedPerson | Group | CareTeam | HealthcareService | BeOrganization) Intended receiver of the communication
. . . sender S Reference ( Device | BePatient | BePractitioner | BePractitionerRole | RelatedPerson | HealthcareService | BeOrganization) The actual sender of the communication
. . . payload S The content of the communication or diary note. Text (up to 320 characters), Attachments (base-64 encoded) or References.
. . . . Slices for content[x] Communication content
Slice: Unordered, Open by type:$this
. . . . . content[x]:contentString string

doco Documentation for this format

Produced 06 Apr 2023