SHIFT SLS Reference Implementation Guide
0.1.0 - ci-build International flag

SHIFT SLS Reference Implementation Guide, published by SHIFT-Task-Force. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/SHIFT-Task-Force/sls-ri-ig/ and changes regularly. See the Directory of published versions

SHIFT SLS-IG Home

Official URL: http://SHIFT-Task-Force.github.io/sls-ri/ImplementationGuide/SHIFT-Task-Force.sls-ri Version: 0.1.0
Active as of 2026-02-05 Computable Name: ShiftSlsRi

This Implementation Guide (IG) contains the resources and profiles necessary to implement the SHIFT Task Force's Shared Legal Standards for Information Exchange (SLS). The SLS provides a framework for sharing health information while respecting patient privacy and legal requirements.

The SHIFT SLS RI GitHub Repository contains the source files for this IG, including FHIR profiles, value sets, and implementation guidance. This is where the details are explained and where the open-source is available.

The FHIR specification provided here is only implemented in the Server mode, not the github pages mode of the SLS-RI.

For discussion of the SLS and ValueSets

Example Patient Data SHIFT Demo Scenarios IG

CapabilityStatement

The Server CapabilityStatement for this FHIR Server implementation can be found here: CapabilityStatement. This is a Requirements CapabilityStatement that outlines the required functionalities for any FHIR server implementing the SLS Reference Implementation.

Initialization Operation

The Server needs to be initialized with ValueSets using the SLS Load ValueSets Operation Definition. This operation populates the server with the necessary ValueSets for proper functioning.

Tagging Data Operation

The Server supports tagging data with legal tags using the SLS Tag Data Operation Definition. This operation allows for the application of legal tags to FHIR resources, ensuring compliance with the SLS framework.