Shared Care Planning (SCP) Implementation Guide
0.2.0 - ci-build
Shared Care Planning (SCP) Implementation Guide - Local Development build (v0.2.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
<Task xmlns="http://hl7.org/fhir">
<id value="cps-task-03-02"/>
<meta>
<versionId value="2"/>
<profile
value="http://santeonnl.github.io/shared-care-planning/StructureDefinition/SCPTask"/>
</meta>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: Task cps-task-03-02</b></p><a name="cps-task-03-02"> </a><a name="hccps-task-03-02"> </a><a name="cps-task-03-02-en-US"> </a><div style="display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px solid #8da1b4; border-radius: 5px; line-height: 60%"><p style="margin-bottom: 0px">version: 2</p><p style="margin-bottom: 0px">Profile: <a href="StructureDefinition-SCPTask.html">Shared Care Planning: Task Profile</a></p></div><p><b>basedOn</b>: <a href="CarePlan-cps-careplan-01.html">CarePlan: status = active; intent = order; category = Multidisciplinary care regime</a></p><p><b>partOf</b>: <a href="Task-cps-task-01.html">Task fullfill</a></p><p><b>status</b>: Completed</p><p><b>intent</b>: order</p><p><b>for</b>: Identifier: <code>http://fhir.nl/fhir/NamingSystem/bsn</code>/111222333</p><p><b>requester</b>: Identifier: <code>http://fhir.nl/fhir/NamingSystem/ura</code>/URA-2</p><p><b>owner</b>: Identifier: <code>http://fhir.nl/fhir/NamingSystem/ura</code>/URA-1</p><blockquote><p><b>input</b></p><p><b>type</b>: <span title="Codes:{http://terminology.hl7.org/CodeSystem/task-input-type Reference}">Reference</span></p><p><b>value</b>: Identifier: <a href="http://terminology.hl7.org/6.0.2/NamingSystem-uri.html" title="As defined by RFC 3986 (http://www.ietf.org/rfc/rfc3986.txt)(with many schemes defined in many RFCs). For OIDs and UUIDs, use the URN form (urn:oid:(note: lowercase) and urn:uuid:). See http://www.ietf.org/rfc/rfc3001.txt and http://www.ietf.org/rfc/rfc4122.txt
This oid is used as an identifier II.root to indicate the the extension is an absolute URI (technically, an IRI). Typically, this is used for OIDs and GUIDs. Note that when this OID is used with OIDs and GUIDs, the II.extension should start with urn:oid or urn:uuid:
Note that this OID is created to aid with interconversion between CDA and FHIR - FHIR uses urn:ietf:rfc:3986 as equivalent to this OID. URIs as identifiers appear more commonly in FHIR.
This OID may also be used in CD.codeSystem.">Uniform Resource Identifier (URI)</a>/urn:oid:2.16.840.1.113883.2.4.3.11.60.909.26.34-2</p></blockquote><blockquote><p><b>input</b></p><p><b>type</b>: <span title="Codes:{http://terminology.hl7.org/CodeSystem/task-input-type Reference}">Reference</span></p><p><b>value</b>: Identifier: <a href="http://terminology.hl7.org/6.0.2/NamingSystem-uri.html" title="As defined by RFC 3986 (http://www.ietf.org/rfc/rfc3986.txt)(with many schemes defined in many RFCs). For OIDs and UUIDs, use the URN form (urn:oid:(note: lowercase) and urn:uuid:). See http://www.ietf.org/rfc/rfc3001.txt and http://www.ietf.org/rfc/rfc4122.txt
This oid is used as an identifier II.root to indicate the the extension is an absolute URI (technically, an IRI). Typically, this is used for OIDs and GUIDs. Note that when this OID is used with OIDs and GUIDs, the II.extension should start with urn:oid or urn:uuid:
Note that this OID is created to aid with interconversion between CDA and FHIR - FHIR uses urn:ietf:rfc:3986 as equivalent to this OID. URIs as identifiers appear more commonly in FHIR.
This OID may also be used in CD.codeSystem.">Uniform Resource Identifier (URI)</a>/urn:oid:2.16.840.1.113883.2.4.3.11.60.909.26.34-3</p></blockquote><blockquote><p><b>output</b></p><p><b>type</b>: <span title="Codes:{http://terminology.hl7.org/CodeSystem/task-input-type Reference}">Reference</span></p><p><b>value</b>: <a href="Bundle-cps-bundle-05.html#urn-uuid-901">Bundle: type = transaction</a></p></blockquote><blockquote><p><b>output</b></p><p><b>type</b>: <span title="Codes:{http://terminology.hl7.org/CodeSystem/task-input-type Reference}">Reference</span></p><p><b>value</b>: <a href="Bundle-cps-bundle-05.html#urn-uuid-902">Bundle: type = transaction</a></p></blockquote></div>
</text>
<basedOn>🔗
<reference value="CarePlan/cps-careplan-01"/>
</basedOn>
<partOf>🔗
<reference value="Task/cps-task-01"/>
</partOf>
<status value="completed"/>
<intent value="order"/>
<for>
<identifier>
<system value="http://fhir.nl/fhir/NamingSystem/bsn"/>
<value value="111222333"/>
</identifier>
</for>
<requester>
<identifier>
<system value="http://fhir.nl/fhir/NamingSystem/ura"/>
<value value="URA-2"/>
</identifier>
</requester>
<owner>
<identifier>
<system value="http://fhir.nl/fhir/NamingSystem/ura"/>
<value value="URA-1"/>
</identifier>
</owner>
<input>
<type>
<coding>
<system
value="http://terminology.hl7.org/CodeSystem/task-input-type"/>
<code value="Reference"/>
<display value="Reference"/>
</coding>
</type>
<valueReference>
<identifier>
<system value="urn:ietf:rfc:3986"/>
<value value="urn:oid:2.16.840.1.113883.2.4.3.11.60.909.26.34-2"/>
</identifier>
</valueReference>
</input>
<input>
<type>
<coding>
<system
value="http://terminology.hl7.org/CodeSystem/task-input-type"/>
<code value="Reference"/>
<display value="Reference"/>
</coding>
</type>
<valueReference>
<identifier>
<system value="urn:ietf:rfc:3986"/>
<value value="urn:oid:2.16.840.1.113883.2.4.3.11.60.909.26.34-3"/>
</identifier>
</valueReference>
</input>
<output>
<type>
<coding>
<system
value="http://terminology.hl7.org/CodeSystem/task-input-type"/>
<code value="Reference"/>
<display value="Reference"/>
</coding>
</type>
<valueReference>
<reference value="urn:uuid:901"/>
</valueReference>
</output>
<output>
<type>
<coding>
<system
value="http://terminology.hl7.org/CodeSystem/task-input-type"/>
<code value="Reference"/>
<display value="Reference"/>
</coding>
</type>
<valueReference>
<reference value="urn:uuid:902"/>
</valueReference>
</output>
</Task>