This page is part of the Personal Health Device FHIR IG (v0.3.0: STU 1 Ballot 3) based on FHIR R4. The current version which supercedes this version is 1.0.0. For a full list of available versions, see the Directory of published versions

PhdServerCapabilityStatement - XML Representation

(back to narrative)

Raw xml

<CapabilityStatement xmlns="http://hl7.org/fhir">
  <id value="PhdServerCapabilityStatement"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml">
     
      <p> Capability Statement for Servers supporting Continua FHIR Observation Clients</p> 
     
      <p> The server supports the upload of the following resource types:</p> 
     
      <ul> 
      
        <li> Patient</li> 
      
        <li> Device</li> 
      
        <li> Observation</li> 
      
        <li> Bundle</li> 
    
      </ul> 
      
      <p> using create, conditional create, update, update-create, and conditional update in either a transaction Bundle or with individual resources.</p> 
      <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> 
    
    </div>
  </text>
  <url
       value="http://hl7.org/fhir/uv/phd/CapabilityStatement/PhdServerCapabilityStatement"/>
  <version value="0.3.0"/>
  <name value="PhdServerCapabilityStatement"/>
  <title value="Continua FHIR Observation Server requirements"/>
  <status value="draft"/>
  <date value="2018-10-27T00:00:00+11:00"/>
  <publisher value="Continua-Personal Connected Health Alliance"/>
  <contact>
    <telecom>
      <system value="url"/>
      <value value="http://hl7.org/fhir"/>
    </telecom>
  </contact>
  <description
               value="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."/>
  <kind value="capability"/>
  <software>
    <name value="Continua FHIR Observation Server"/>
  </software>
  <fhirVersion value="4.0.0"/>
  <format value="json"/>
  <format value="xml"/>
  <rest>
    <mode value="server"/>
    <documentation value="Continua FHIR Observation Server requirements"/>
    <security>
      <service>
        <coding>
          <system
                  value="http://terminology.hl7.org/CodeSystem/restful-security-service"/>
          <code value="OAuth"/>
        </coding>
        <coding>
          <system
                  value="http://terminology.hl7.org/CodeSystem/restful-security-service"/>
          <code value="Basic"/>
        </coding>
      </service>
      <description value="Describe the oauth model ..."/>
    </security>
    <resource>
      <type value="Bundle"/>
      <documentation
                     value="The server is required to support the transaction Bundle and the resolution of temporary logical ids."/>
      <interaction>
        <code value="create"/>
      </interaction>
    </resource>
    <resource>
      <type value="Patient"/>
      <documentation
                     value="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 value="update"/>
      </interaction>
      <interaction>
        <code value="create"/>
      </interaction>
      <updateCreate value="true"/>
      <conditionalCreate value="true"/>
      <conditionalUpdate value="true"/>
    </resource>
    <resource>
      <type value="Device"/>
      <interaction>
        <code value="update"/>
      </interaction>
      <interaction>
        <code value="create"/>
      </interaction>
      <updateCreate value="true"/>
      <conditionalCreate value="true"/>
      <conditionalUpdate value="true"/>
    </resource>
    <resource>
      <type value="Observation"/>
      <interaction>
        <code value="create"/>
      </interaction>
      <conditionalCreate value="true"/>
    </resource>
    <interaction>
      <code value="transaction"/>
    </interaction>
  </rest>
</CapabilityStatement>