<status value="draft" /> <date value="2018-03-24T00:44:38.512-04:00" /> <publisher value="SAMHSA" /> <contact> <name value="Neelima Chennamaraja" /> <telecom> <system value="url" /> <value value="www.eversolve.com" /> <period> <start value="1999-06-15" /> </period> </telecom> <telecom> <system value="email" /> <value value="neelima@eversolve.com" /> <use value="work" /> </telecom> </contact> <description value="This OCP (Omnibus Care Plan) Communication profile describes an occurrence of information being transmitted. A communication is a conveyance of information from one entity, a sender, to another entity, a receiver and the information is delivered only once. The sender and receivers may be patients, practitioners, related persons, organizations, or devices. It identifies which core elements, extensions, and value sets SHALL be present in the resource when using this profile. Communication does not deal with the duration of a call, it represents the fact that information was transferred at a particular point in time." /> <jurisdiction> <coding> <code value="US" /> <display value="US-Realm" /> </coding> <text value="US-Realm OCP EpisodeOfCare Profile published by SAMHSA" /> </jurisdiction> <purpose value="This profile for Communication includes all the elements related to basic need for OCP (which could change over time). This profile is intended to be implemented by OCP (Omnibus Care Plan) systems." /> <copyright value="+Copyright (c) 2017 SAMHSA. All Rights Reserved." /> <fhirVersion value="3.0.1" /> <kind value="resource" /> <abstract value="false" /> <type value="Communication" /> <baseDefinition value="http://hl7.org/fhir/StructureDefinition/Communication" /> <derivation value="constraint" /> <differential> <element id="Communication.definition"> <path value="Communication.definition" /> <definition value="A protocol, guideline, or other definition that was adhered to in whole or in part by this communication event. To be supported later once organization relationship is established. There could be one or more ActivityDefinition templates defined for Communication (e.g. Outreach)." /> <max value="1" /> <mustSupport value="true" /> </element> <element id="Communication.status"> <path value="Communication.status" /> <definition value="The status of the transmission. Show all status for user to choose from. May require state machine flow for this." /> <type> <code value="code" /> <profile value="http://hl7.org/fhir/StructureDefinition/code" /> </type> <mustSupport value="true" /> </element> <element id="Communication.notDone"> <path value="Communication.notDone" /> <definition value="If true, indicates that the described communication event did not actually occur. Allow user to check if the communication did not occur and this is added just for record person (e.g. tried calling Patient but was not able to talk). Default value is FALSE." /> <min value="1" /> <type> <code value="boolean" /> <profile value="http://hl7.org/fhir/StructureDefinition/boolean" /> </type> <mustSupport value="true" /> </element> <element id="Communication.notDoneReason"> <path value="Communication.notDoneReason" /> <definition value="Describes why the communication event did not occur in coded and/or textual form. Allow user to choose from value set. Only required if notDone = true." /> <mustSupport value="true" /> </element> <element id="Communication.category"> <path value="Communication.category" /> <comment value="There may be multiple axes of categorization and one communication may serve multiple purposes. Allow user to choose from value set. Use FHIR example value set for now." /> <min value="1" /> <max value="1" /> <type> <code value="CodeableConcept" /> <profile value="http://hl7.org/fhir/StructureDefinition/CodeableConcept" /> </type> <mustSupport value="true" /> </element> <element id="Communication.medium"> <path value="Communication.medium" /> <definition value="A channel that was used for this communication (e.g. email, fax). Allow user to choose from value set. Use FHIR example value set for now." /> <min value="1" /> <max value="1" /> <type> <code value="CodeableConcept" /> <profile value="http://hl7.org/fhir/StructureDefinition/CodeableConcept" /> </type> <mustSupport value="true" /> </element> <element id="Communication.subject"> <path value="Communication.subject" /> <definition value="The patient or group that was the focus of this communication. System populated with the current patient context when communication is created specific to Patient." /> <type> <code value="Reference" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/Group" /> </type> <type> <code value="Reference" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/ocp-patient" /> </type> <mustSupport value="true" /> </element> <element id="Communication.recipient"> <path value="Communication.recipient" /> <definition value="The entity (e.g. person, organization, clinical information system, 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). Patient or Practitioner from Care Team or RelatedPerson associated with the Patient (may or may not be in the Care Team)." /> <min value="1" /> <type> <code value="Reference" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/Organization" /> </type> <type> <code value="Reference" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/Group" /> </type> <type> <code value="Reference" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/ocp-patient" /> </type> <type> <code value="Reference" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/ocp-practitioner" /> </type> <type> <code value="Reference" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/ocp-relatedperson" /> </type> <mustSupport value="true" /> </element> <element id="Communication.topic"> <path value="Communication.topic" /> <definition value="The resources which were responsible for or related to producing this communication. System to populate with Task or Appointment or CarePlan etc. depending on where creation of Communication is invoked from. Optional link to other resource such as Task/Activity, Assessment, Care Plan, Appointment etc." /> <max value="1" /> <mustSupport value="true" /> </element> <element id="Communication.context"> <path value="Communication.context" /> <definition value="The encounter within which the communication was sent. Select from list of Episode of Care (same way as on Task) for current patient context and current organization cotext. Generally there should be only one active Episode of Care for given patient and organization. Keeping it optional to allow communication that is not related to specific episode of care." /> <type> <code value="Reference" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/Encounter" /> </type> <type> <code value="Reference" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/ocp-episodeofcare" /> </type> <mustSupport value="true" /> </element> <element id="Communication.sent"> <path value="Communication.sent" /> <definition value="The time when this communication was sent. When communication was made or message was sent. Populated by the system with current date/time by default but allow user to choose different datetime in the past if user is entering afterwards." /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Communication.received"> <path value="Communication.received" /> <definition value="The time when this communication arrived at the destination. Adding to profile and may be used later for receipient to acknoledge receipt when applicable." /> <mustSupport value="true" /> </element> <element id="Communication.sender"> <path value="Communication.sender" /> <definition value="The entity (e.g. person, organization, clinical information system, or device) which was the source of the communication. Read-only. System populated with the current user context (usually Practitioner but could be Patient or RelatedPerson). May not need to support Organization or Device." /> <min value="1" /> <type> <code value="Reference" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/Organization" /> </type> <type> <code value="Reference" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/ocp-patient" /> </type> <type> <code value="Reference" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/ocp-practitioner" /> </type> <type> <code value="Reference" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/ocp-relatedperson" /> </type> <mustSupport value="true" /> </element> <element id="Communication.payload"> <path value="Communication.payload" /> <definition value="Text, attachment(s), or resource(s) that was communicated to the recipient. Allow user to enter optional message text if applicable (e.g. not needed for phone conversation)." /> <min value="1" /> <max value="1" /> <mustSupport value="true" /> </element> <element id="Communication.payload.content[x]"> <path value="Communication.payload.content[x]" /> <definition value="A communicated content (or for multi-part communications, one portion of the communication). Only use string for now. May be used at later time to include attachments." /> <mustSupport value="true" /> </element> <element id="Communication.note"> <path value="Communication.note" /> <definition value="Additional notes or commentary about the communication by the sender, receiver or other interested parties. Optional comments not part of the message." /> <max value="1" /> <mustSupport value="true" /> </element> </differential> </StructureDefinition>

The FHIR STU3 (Release 3) Omnibus Care Plan (OCP) Communication profile uses FHIR resources and describes minimum expectations for the Communication with supported data elements and changes to the cardinality. It identifies which core elements, extensions, and value sets SHALL be present in the resource when using this profile. The Communication is about the transfer of information (which may or may not occur as part of an encounter). Phone calls not involving the patient (e.g. between practitioners or practitioner to relative) that are tracked for billing or other purposes can use Communication to represent the information transferred, but are not ideal to represent the call itself. Dependencies: Communication profile that conform to this specification must include reference to other resources

OCP-Patient
Group
Organization
ActivityDefinition
PlanDefinition
OCP-Practitioner
OCP-RelatedPerson
EpisodeOfCare
Encounter
Condition
Observation