R4 Ballot #1 (Mixed Normative/Trial use)

This page is part of the FHIR Specification (v3.3.0: R4 Ballot 2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4B R4 R3

Codesystem-extra-security-role-type.xml

Vocabulary Work GroupMaturity Level: N/ABallot Status: Informative

Raw XML (canonical form)

Definition for Code System SecurityRoleType

<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="extra-security-role-type"/> 
  <meta> 
    <lastUpdated value="2018-04-03T12:05:46.262+10:00"/> 
    <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"/> 
  </meta> 
  <text> 
    <status value="generated"/> 
    <div xmlns="http://www.w3.org/1999/xhtml"> 
      <hr/>  
      <h2> SecurityRoleType</h2> 
      <div> 
        <p> This CodeSystem contains Additional FHIR-defined Security Role types not defined elsewhere</p> 

      </div> 
      <p> This code system http://hl7.org/fhir/extra-security-role-type defines the following codes:</p> 
      <table class="codes">
        <tr> 
          <td style="white-space:nowrap">
            <b> Code</b> 
          </td> 
          <td> 
            <b> Display</b> 
          </td> 
          <td> 
            <b> Definition</b> 
          </td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">authserver
            <a name="extra-security-role-type-authserver"> </a> 
          </td> 
          <td> authorization server</td> 
          <td> An entity providing authorization services to enable the electronic sharing of health-related
             information based on resource owner's preapproved permissions. For example, an UMA Authorization
             Server[UMA]</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">datacollector
            <a name="extra-security-role-type-datacollector"> </a> 
          </td> 
          <td> data collector</td> 
          <td> An entity that collects information over which the data subject may have certain rights
             under policy or law to control that information's management and distribution by data
             collectors, including the right to access, retrieve, distribute, or delete that information.
             </td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">dataprocessor
            <a name="extra-security-role-type-dataprocessor"> </a> 
          </td> 
          <td> data processor</td> 
          <td> An entity that processes collected information over which the data subject may have certain
             rights under policy or law to control that information's management and distribution by
             data processors, including the right to access, retrieve, distribute, or delete that information.</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">datasubject
            <a name="extra-security-role-type-datasubject"> </a> 
          </td> 
          <td> data subject</td> 
          <td> A person whose personal information is collected or processed, and who may have certain
             rights under policy or law to control that information's management and distribution by
             data collectors or processors, including the right to access, retrieve, distribute, or
             delete that information.</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">humanuser
            <a name="extra-security-role-type-humanuser"> </a> 
          </td> 
          <td> human user</td> 
          <td> The human user that has participated.</td> 
        </tr> 
      </table> 
    </div> 
  </text> 
  <url value="http://hl7.org/fhir/extra-security-role-type"/> 
  <version value="3.3.0"/> 
  <name value="SecurityRoleType"/> 
  <status value="draft"/> 
  <experimental value="true"/> 
  <date value="2017-02-13"/> 
  <publisher value="HL7 International"/> 
  <contact> 
    <name value="FHIR project team"/> 
    <telecom> 
      <system value="url"/> 
      <value value="http://hl7.org/fhir"/> 
    </telecom> 
  </contact> 
  <description value="This CodeSystem contains Additional FHIR-defined Security Role types not defined elsewhere"/> 
  <caseSensitive value="true"/> 
  <content value="complete"/> 
  <concept> 
    <code value="authserver"/> 
    <display value="authorization server"/> 
    <definition value="An entity providing authorization services to enable the electronic sharing of health-related
     information based on resource owner's preapproved permissions. For example, an UMA Authorization
     Server[UMA]"/> 
  </concept> 
  <concept> 
    <code value="datacollector"/> 
    <display value="data collector"/> 
    <definition value="An entity that collects information over which the data subject may have certain rights
     under policy or law to control that information's management and distribution by data
     collectors, including the right to access, retrieve, distribute, or delete that information.
     "/> 
  </concept> 
  <concept> 
    <code value="dataprocessor"/> 
    <display value="data processor"/> 
    <definition value="An entity that processes collected information over which the data subject may have certain
     rights under policy or law to control that information's management and distribution by
     data processors, including the right to access, retrieve, distribute, or delete that information."/> 
  </concept> 
  <concept> 
    <code value="datasubject"/> 
    <display value="data subject"/> 
    <definition value="A person whose personal information is collected or processed, and who may have certain
     rights under policy or law to control that information's management and distribution by
     data collectors or processors, including the right to access, retrieve, distribute, or
     delete that information."/> 
  </concept> 
  <concept> 
    <code value="humanuser"/> 
    <display value="human user"/> 
    <definition value="The human user that has participated."/> 
  </concept> 
</CodeSystem> 

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.