Cancer Pathology Data Sharing
2.0.0 - STU 2

Cancer Pathology Data Sharing, published by HL7 International / Orders and Observations. This guide is not an authorized publication; it is the continuous build for version 2.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/cancer-reporting/ and changes regularly. See the Directory of published versions

## CapabilityStatement: Pathology Laboratory Information System

Official URL: http://hl7.org/fhir/us/cancer-reporting/CapabilityStatement/capabilitystatement-pathology-lab-information-system | Version: 2.0.0
Standards status: Trial-use | Maturity Level: 2 | Computable Name: PathologyLabInformationSystem

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.

Raw OpenAPI-Swagger Definition file | Download

## Pathology Laboratory Information System

- Implementation Guide Version: 2.0.0
- FHIR Version: 4.0.1
- Supported Formats: `json`, `xml`
- Published on: 2022-06-13
- Published by: HL7 International / Orders and Observations

> Note to Implementers: FHIR Capabilities

> 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.

## FHIR RESTful Capabilities

### Mode: `server`

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

> Implementations must meet the general security requirements documented in the security section of the implementation guide.

### Capabilities by Resource/Profile

#### Summary

The summary table lists the resources that are part of this configuration, and for each resource it lists:

- The relevant profiles (if any)
- The interactions supported by each resource (Read, Search, Update, and Create, are always shown, while VRead, Patch, Delete, History on Instance, or History on Type are only present if at least one of the resources has support for them.
- The required, recommended, and some optional search parameters (if any).
- The linked resources enabled for `_include`
- The other resources enabled for `_revinclude`
- The operations on the resource (if any)

Resource Type | Profile | R | S | U | C | D | Searches | `_include` | `_revinclude` | Operations
--- | --- | --- | --- | --- | --- | --- | --- | --- | --- | ---
DiagnosticReport |  | y |  | y | y | y |  |  |  |

#### Resource Conformance: supported DiagnosticReport

Core FHIR Resource
DiagnosticReport
Reference Policy
Interaction summary

- Supports
  `read`

  Allows retrieval of a specific DiagnosticReport instance.

  `create`

  Allows creation of a DiagnosticReport resource instance.

  `update`

  Allows update of a DiagnosticReport resource instance.

  `delete`

  Allows deletion of a DiagnosticReport resource instance.