Cancer Pathology Data Sharing
1.0.1 - STU 1.0.1 United States of America flag

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 in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

CapabilityStatement: Pathology Laboratory Information System

Official URL: http://hl7.org/fhir/us/cancer-reporting/CapabilityStatement/pathology-lab-information-system Version: 1.0.1
Draft as of 2022-06-13 Computable Name: PathologyLabInformationSystem

Copyright/Legal:

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: 1.0.1
  • FHIR Version: 4.0.1
  • Supported Formats: json, xml
  • Supported Patch Formats:
  • 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.

Summary of System-wide Interactions

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 TypeProfileRSUCDSearches_include_revincludeOperations
DiagnosticReport yyyy

Resource Conformance: supportedDiagnosticReport

Core FHIR Resource
DiagnosticReport
Reference Policy
Interaction summary
  • Supports read, create, update, delete.