Personal Health Device Implementation Guide
1.1.0 - STU 1.1 International flag

Personal Health Device Implementation Guide, published by HL7 International / Health Care Devices. This guide is not an authorized publication; it is the continuous build for version 1.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/phd/ and changes regularly. See the Directory of published versions

CapabilityStatement: PhdServerCapabilityStatement

Official URL: http://hl7.org/fhir/uv/phd/CapabilityStatement/PhdServerCapabilityStatement Version: 1.1.0
Draft as of 2018-10-27 Computable Name: PhdServerCapabilityStatement

Specifies the capabilities of a server supporting the Continua FHIR Observation Server class. The Continua FHIR Observation Server supports the Continua FHIR Observation Client as specified in the Continua H.812-5 Design Guidelines. This class of uploaders transcodes data from medical devices following the IEEE 11073-10206 data model to FHIR as profiled in the Personal Health Device Implementation Guide with the authentication, security, and transaction protocols specified in H.812-5. The Continua FHIR Observation Server is a RESTFul FHIR server subject to the additional requirements of H.812-5. This capability statement specifies only those capabilities needed to receive data from a Continua FHIR Observation Client.

Raw OpenAPI-Swagger Definition file | Download

Generated Narrative: CapabilityStatement PhdServerCapabilityStatement

Continua FHIR Observation Server requirements

  • Implementation Guide Version: 1.1.0
  • FHIR Version: 4.0.1
  • Supported Formats: json, xml
  • Supported Patch Formats:
  • Published on: 2018-10-27
  • Published by: HL7 International / Health Care Devices

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

Continua FHIR Observation Server requirements

Security
Enable CORS: no
Security services supported: OAuth

Describe the oauth model ...

Summary of System-wide Interactions
  • Supports the transactioninteraction.

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 TypeProfileRSUCSearches_include_revincludeOperations
Bundle y
Patient yy
Device yy
Observation y

Resource Conformance: supported Bundle

Core FHIR Resource
Bundle
Reference Policy
Interaction summary
  • Supports create.

Documentation

The server is required to support the transaction Bundle and the resolution of temporary logical ids.

Resource Conformance: supported Patient

Core FHIR Resource
Patient
Reference Policy
Interaction summary
  • Supports update, create.

Documentation

A server may refuse the upload of a Patient resource to protect Personal Health Information (PHI). Administrators of such servers provide the uploader the logical id of the Patient resource by an unspecified means. The client uses the logical id in its Observation resources as needed. The Patient resource may or may not exist on the server but the Observation resource shall not be rejected by the server due to a resource not found error if it uses the provided logical id. In those situations where the Patient resource is uploaded by the client the resource is only required to contain an opaque identifier. In this manner, PHI is still protected as only the service provider has the key linking the identifier to an actual patient.

Resource Conformance: supported Device

Core FHIR Resource
Device
Reference Policy
Interaction summary
  • Supports update, create.

Resource Conformance: supported Observation

Core FHIR Resource
Observation
Reference Policy
Interaction summary
  • Supports create.