Personal Health Device Implementation Guide
1.0.0 - STU 1

This page is part of the Personal Health Device FHIR IG (v1.0.0: STU 1) based on FHIR 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

: PhdServerCapabilityStatement - JSON Representation

Raw json | Download


{
  "resourceType" : "CapabilityStatement",
  "id" : "PhdServerCapabilityStatement",
  "text" : {
    "status" : "generated",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n     \n      <p> Capability Statement for Servers supporting Continua FHIR Observation Clients</p> \n     \n      <p> The server supports the upload of the following resource types:</p> \n     \n      <ul> \n      \n        <li> Patient</li> \n      \n        <li> Device</li> \n      \n        <li> Observation</li> \n      \n        <li> Bundle</li> \n    \n      </ul> \n      \n      <p> using create, conditional create, update, update-create, and conditional update in either a transaction Bundle or with individual resources.</p> \n      <p> A server may refuse the upload of a Patient resource in the special case where the service administrator provides the logical id of the Patient resource to the uploader so it may be used in the uploaded Observation resources. This option gives extra protection of Personal Health Information.</p> \n    \n    </div>"
  },
  "url" : "http://hl7.org/fhir/uv/phd/CapabilityStatement/PhdServerCapabilityStatement",
  "version" : "1.0.0",
  "name" : "PhdServerCapabilityStatement",
  "title" : "Continua FHIR Observation Server requirements",
  "status" : "draft",
  "date" : "2018-10-27",
  "publisher" : "HL7 International - Health Care Devices Work Group",
  "contact" : [
    {
      "telecom" : [
        {
          "system" : "url",
          "value" : "http://hl7.org/Special/committees/healthcaredevices"
        }
      ]
    }
  ],
  "description" : "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 20601 data model to FHIR as profiled in the Continua 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.",
  "jurisdiction" : [
    {
      "coding" : [
        {
          "system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code" : "001"
        }
      ]
    }
  ],
  "kind" : "capability",
  "software" : {
    "name" : "Continua FHIR Observation Server"
  },
  "fhirVersion" : "4.0.0",
  "format" : [
    "json",
    "xml"
  ],
  "rest" : [
    {
      "mode" : "server",
      "documentation" : "Continua FHIR Observation Server requirements",
      "security" : {
        "service" : [
          {
            "coding" : [
              {
                "system" : "http://terminology.hl7.org/CodeSystem/restful-security-service",
                "code" : "OAuth"
              },
              {
                "system" : "http://terminology.hl7.org/CodeSystem/restful-security-service",
                "code" : "Basic"
              }
            ]
          }
        ],
        "description" : "Describe the oauth model ..."
      },
      "resource" : [
        {
          "type" : "Bundle",
          "documentation" : "The server is required to support the transaction Bundle and the resolution of temporary logical ids.",
          "interaction" : [
            {
              "code" : "create"
            }
          ]
        },
        {
          "type" : "Patient",
          "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.",
          "interaction" : [
            {
              "code" : "update"
            },
            {
              "code" : "create"
            }
          ],
          "updateCreate" : true,
          "conditionalCreate" : true,
          "conditionalUpdate" : true
        },
        {
          "type" : "Device",
          "interaction" : [
            {
              "code" : "update"
            },
            {
              "code" : "create"
            }
          ],
          "updateCreate" : true,
          "conditionalCreate" : true,
          "conditionalUpdate" : true
        },
        {
          "type" : "Observation",
          "interaction" : [
            {
              "code" : "create"
            }
          ],
          "conditionalCreate" : true
        }
      ],
      "interaction" : [
        {
          "code" : "transaction"
        }
      ]
    }
  ]
}