This page is part of the Sharing eCC Data from Pathology Labs to EHR (v1.0.1: STU 1) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions
Draft as of 2022-06-13 |
<CapabilityStatement xmlns="http://hl7.org/fhir">
<id value="pathology-lab-information-system"/>
<meta>
<versionId value="1"/>
<lastUpdated value="2022-06-16T20:38:40.839+00:00"/>
<source value="#8miJe7tKT3dc93yA"/>
</meta>
<text>
<status value="extensions"/>
<div xmlns="http://www.w3.org/1999/xhtml"><h2 id="title">Pathology Laboratory Information System</h2><ul><li>Implementation Guide Version: 1.0.1</li><li>FHIR Version: 4.0.1</li><li>Supported Formats: <code>json</code>, <code>xml</code></li><li>Supported Patch Formats: </li><li>Published on: 2022-06-13</li><li>Published by: HL7 International / Orders and Observations</li></ul><blockquote class="impl-note"><p><strong>Note to Implementers: FHIR Capabilities</strong></p><p>Any FHIR capability may be 'allowed' by the system unless explicitly marked as "SHALL NOT". A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.</p></blockquote><h2 id="rest">FHIR RESTful Capabilities</h2><div class="panel panel-default"><div class="panel-heading"><h3 id="mode1" class="panel-title">Mode: <code>server</code></h3></div><div class="panel-body"><div><p>The focus of the EHR is to allow creation, modification and deletion of DiagnosticReports and allows searching and retrieval of resources using US Core APIs.</p>
</div><div class="lead"><em>Security</em></div><blockquote><div><p>Implementations must meet the general security requirements documented in the security section of the implementation guide.</p>
</div></blockquote><div class="lead"><em>Summary of System-wide Interactions</em></div></div></div><h3 id="resourcesCap1">Capabilities by Resource/Profile</h3><h4 id="resourcesSummary1">Summary</h4><p>The summary table lists the resources that are part of this configuration, and for each resource it lists:</p><ul><li>The relevant profiles (if any)</li><li>The interactions supported by each resource (<b><span class="bg-info">R</span></b>ead, <b><span class="bg-info">S</span></b>earch, <b><span class="bg-info">U</span></b>pdate, and <b><span class="bg-info">C</span></b>reate, are always shown, while <b><span class="bg-info">VR</span></b>ead, <b><span class="bg-info">P</span></b>atch, <b><span class="bg-info">D</span></b>elete, <b><span class="bg-info">H</span></b>istory on <b><span class="bg-info">I</span></b>nstance, or <b><span class="bg-info">H</span></b>istory on <b><span class="bg-info">T</span></b>ype are only present if at least one of the resources has support for them.</li><li><span>The required, recommended, and some optional search parameters (if any). </span></li><li>The linked resources enabled for <code>_include</code></li><li>The other resources enabled for <code>_revinclude</code></li><li>The operations on the resource (if any)</li></ul><div class="table-responsive"><table class="table table-condensed table-hover"><thead><tr><th><b>Resource Type</b></th><th><b>Profile</b></th><th class="text-center"><b title="GET a resource (read interaction)">R</b></th><th class="text-center"><b title="GET all set of resources of the type (search interaction)">S</b></th><th class="text-center"><b title="PUT a new resource version (update interaction)">U</b></th><th class="text-center"><b title="POST a new resource (create interaction)">C</b></th><th class="text-center"><b title="DELETE a resource (delete interaction)">D</b></th><th><b title="Required and recommended search parameters">Searches</b></th><th><code><b>_include</b></code></th><th><code><b>_revinclude</b></code></th><th><b>Operations</b></th></tr></thead><tbody><tr><td><a href="#DiagnosticReport1-1">DiagnosticReport</a></td><td> </td><td>y</td><td class="text-center"></td><td class="text-center">y</td><td class="text-center">y</td><td class="text-center">y</td><td></td><td/><td/><td/></tr></tbody></table></div><hr/><div class="panel panel-default"><div class="panel-heading"><h4 id="DiagnosticReport1-1" class="panel-title"><span style="float: right;">Resource Conformance: supported</span>DiagnosticReport</h4></div><div class="panel-body"><div class="container"><div class="row"><div class="col-lg-4"><span class="lead">Core FHIR Resource</span><br/><a href="http://hl7.org/fhir/R4/diagnosticreport.html">DiagnosticReport</a></div><div class="col-lg-4"><span class="lead">Reference Policy</span><br/></div><div class="col-lg-4"><span class="lead">Interaction summary</span><br/><ul><li>Supports <code>read</code>, <code>create</code>, <code>update</code>, <code>delete</code>.</li></ul></div></div><p/><p/></div></div></div></div>
</text>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
<valueCode value="oo"/>
</extension>
<url
value="http://hl7.org/fhir/us/cancer-reporting/CapabilityStatement/pathology-lab-information-system"/>
<version value="1.0.1"/>
<name value="PathologyLabInformationSystem"/>
<title value="Pathology Laboratory Information System"/>
<status value="draft"/>
<experimental value="false"/>
<date value="2022-06-13"/>
<publisher value="HL7 International / Orders and Observations"/>
<contact>
<name value="HL7 International - Orders and Observations"/>
<telecom>
<system value="url"/>
<value value="http://www.hl7.org/Special/committees/orders"/>
</telecom>
</contact>
<description
value="This profile defines the expected capabilities of the ''LIS'' actor when conforming to the Cancer Pathology Data Sharing Guide. This role is responsible for allowing creation, modification and deletion of DiagnosticReports and allows searching and retrieval of resources using US Core APIs."/>
<jurisdiction>
<coding>
<system value="urn:iso:std:iso:3166"/>
<code value="US"/>
<display value="United States of America"/>
</coding>
<text value="United States of America"/>
</jurisdiction>
<copyright
value="<copyright value="This material contains content from LOINC (http://loinc.org ). Refer to terminology.hl7.org for copyright information. LOINC® is available at no cost under the license at http://loinc.org/license . LOINC® is a registered United States trademark of Regenstrief Institute, Inc."/>"/>
<kind value="requirements"/>
<fhirVersion value="4.0.1"/>
<format value="json"/>
<format value="xml"/>
<rest>
<mode value="server"/>
<documentation
value="The focus of the EHR is to allow creation, modification and deletion of DiagnosticReports and allows searching and retrieval of resources using US Core APIs."/>
<security>
<description
value="Implementations must meet the general security requirements documented in the security section of the implementation guide."/>
</security>
<resource>
<type value="DiagnosticReport"/>
<interaction>
<code value="read"/>
<documentation
value="Allows retrieval of a specific DiagnosticReport instance."/>
</interaction>
<interaction>
<code value="create"/>
<documentation
value="Allows creation of a DiagnosticReport resource instance."/>
</interaction>
<interaction>
<code value="update"/>
<documentation
value="Allows update of a DiagnosticReport resource instance."/>
</interaction>
<interaction>
<code value="delete"/>
<documentation
value="Allows deletion of a DiagnosticReport resource instance."/>
</interaction>
</resource>
</rest>
</CapabilityStatement>