Valueset-object-role.xml Raw XML (

Definition for Value SetAuditEventObjectRole

<ValueSet xmlns="http://hl7.org/fhir">
  <id value="object-role"/>
  <meta>
    

    <lastUpdated value="2016-03-31T08:01:25.570+11:00"/>
    <profile value="http://hl7.org/fhir/StructureDefinition/valueset-shareable-definition"/>
  </meta>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml">
      <h2>AuditEventObjectRole</h2>
      <p>Code representing the role the Object played in the event.</p>
      This value set has an inline code system http://hl7.org/fhir/object-role, which defines
         the following codes:
      
        
          
            
          
          
            
          
          
            
          
        
        
          1
            
          
          
          This object is the patient that is the subject of care related to this event.  It is identifiable
             by patient ID or equivalent.  The patient may be either human or animal.
        
        
          2
            
          
          
          This is a location identified as related to the event.  This is usually the location where
             the event took place.  Note that for shipping, the usual events are arrival at a location
             or departure from a location.
        
        
          3
            
          
          
          This object is any kind of persistent document created as a result of the event.  This
             could be a paper report, film, electronic report, DICOM Study, etc.  Issues related to
             medical records life cycle management are conveyed elsewhere.
        
        
          4
            
          
          
          A logical object related to a health record event.  This is any healthcare  specific resource
             (object) not restricted to FHIR defined Resources.
        
        
          5
            
          
          
          This is any configurable file used to control creation of documents.  Examples include
             the objects maintained by the HL7 Master File transactions, Value Sets, etc.
        
        
          6
            
          
          
          
        
        
          7
            
          
          
          
        
        
          8
            
          
          
          Typically a licensed person who is providing or performing care related to the event,
             generally a physician.   The key distinction between doctor and practitioner is with regards
             to their role, not the licensing.  The doctor is the human who actually performed the
             work.  The practitioner is the human or organization that is responsible for the work.
        
        
          9
            
          
          
          A person or system that is being notified as part of the event.  This is relevant in situations
             where automated systems provide notifications to other parties when an event took place.
        
        
          10
            
          
          
          Insurance company, or any other organization who accepts responsibility for paying for
             the healthcare event.
        
        
          11
            
          
          
          
        
        
          12
            
          
          
          A person or system object involved in the event with the authority to modify security
             roles of other objects.
        
        
          13
            
          
          
          
        
        
          14
            
          
          
          
        
        
          15
            
          
          
          Any person or organization responsible for providing care.  This encompasses all forms
             of care, licensed or otherwise, and all sorts of teams and care groups. Note, the distinction
             between practitioners and the doctor that actually provided the care to the patient.
        
        
          16
            
          
          
          
        
        
          17
            
          
          
          A source or destination for data transfer that acts as an archive, database, or similar
             role.
        
        
          18
            
          
          
          An object that holds schedule information.  This could be an appointment book, availability
             information, etc.
        
        
          19
            
          
          
          An organization or person that is the recipient of services.  This could be an organization
             that is buying services for a patient, or a person that is buying services for an animal.
        
        
          20
            
          
          
          An order, task, work item, procedure step, or other description of work to be performed;
             e.g. a particular instance of an MPPS.
        
        
          21
            
          
          
          
        
        
          22
            
          
          
          
        
        
          23
            
          
          
          An object that specifies or controls the routing or delivery of items.  For example, a
             distribution list is the routing criteria for mail.  The items delivered may be documents,
             jobs, or other objects.
        
        
          24
            
          
          
          The contents of a query.  This is used to capture the contents of any kind of query. 
             For security surveillance purposes knowing the queries being made is very important.
        
      

      <p>
        <b>Copyright Statement:</b> These codes are excerpted from Digital Imaging and Communications in Medicine (DICOM)
         Standard, Part 16: Content Mapping Resource, Copyright © 2011 by the National Electrical
         Manufacturers Association.
      </p>
      <p>This value set includes codes from the following code systems:</p>
      <ul>
        <li>Include all codes defined in 
          <a href="codesystem-object-role.html">http://hl7.org/fhir/object-role</a>
        </li>
      </ul>
    </div>
  </text>
  <extension url="http://hl7.org/fhir/StructureDefinition/valueset-oid">
    <valueUri value="urn:oid:2.16.840.1.113883.4.642.2.267"/>
  </extension>
  <url value="http://hl7.org/fhir/ValueSet/object-role"/>
  

  <version value="1.4.0"/>
  <name value="AuditEventObjectRole"/>
  <status value="draft"/>
  <experimental value="false"/>
  <publisher value="HL7 (FHIR Project)"/>
  <contact>
    <telecom>
      <system value="other"/>
      <value value="http://hl7.org/fhir"/>
    </telecom>
    <telecom>
      <system value="email"/>
      <value value="fhir@lists.hl7.org"/>
    </telecom>
  </contact>
  

  <date value="2016-03-31T08:01:25+11:00"/>
  <description value="Code representing the role the Object played in the event."/>
  
    
      
    
    
    
    
    
      
      
      This object is the patient that is the subject of care related to this event.  It is identifiable
       by patient ID or equivalent.  The patient may be either human or animal.
    
    
      
      
      This is a location identified as related to the event.  This is usually the location where
       the event took place.  Note that for shipping, the usual events are arrival at a location
       or departure from a location.
    
    
      
      
      This object is any kind of persistent document created as a result of the event.  This
       could be a paper report, film, electronic report, DICOM Study, etc.  Issues related to
       medical records life cycle management are conveyed elsewhere.
    
    
      
      
      A logical object related to a health record event.  This is any healthcare  specific resource
       (object) not restricted to FHIR defined Resources.
    
    
      
      
      This is any configurable file used to control creation of documents.  Examples include
       the objects maintained by the HL7 Master File transactions, Value Sets, etc.
    
    
      
      
      
    
    
      
      
      
    
    
      
      
      Typically a licensed person who is providing or performing care related to the event,
       generally a physician.   The key distinction between doctor and practitioner is with regards
       to their role, not the licensing.  The doctor is the human who actually performed the
       work.  The practitioner is the human or organization that is responsible for the work.
    
    
      
      
      A person or system that is being notified as part of the event.  This is relevant in situations
       where automated systems provide notifications to other parties when an event took place.
    
    
      
      
      Insurance company, or any other organization who accepts responsibility for paying for
       the healthcare event.
    
    
      
      
      
    
    
      
      
      A person or system object involved in the event with the authority to modify security
       roles of other objects.
    
    
      
      
      
    
    
      
      
      
    
    
      
      
      Any person or organization responsible for providing care.  This encompasses all forms
       of care, licensed or otherwise, and all sorts of teams and care groups. Note, the distinction
       between practitioners and the doctor that actually provided the care to the patient.
    
    
      
      
      
    
    
      
      
      A source or destination for data transfer that acts as an archive, database, or similar
       role.
    
    
      
      
      An object that holds schedule information.  This could be an appointment book, availability
       information, etc.
    
    
      
      
      An organization or person that is the recipient of services.  This could be an organization
       that is buying services for a patient, or a person that is buying services for an animal.
    
    
      
      
      An order, task, work item, procedure step, or other description of work to be performed;
       e.g. a particular instance of an MPPS.
    
    
      
      
      
    
    
      
      
      
    
    
      
      
      An object that specifies or controls the routing or delivery of items.  For example, a
       distribution list is the routing criteria for mail.  The items delivered may be documents,
       jobs, or other objects.
    
    
      
      
      The contents of a query.  This is used to capture the contents of any kind of query. 
       For security surveillance purposes knowing the queries being made is very important.
    
  

  <copyright value="These codes are excerpted from Digital Imaging and Communications in Medicine (DICOM)
   Standard, Part 16: Content Mapping Resource, Copyright © 2011 by the National Electrical
   Manufacturers Association."/>
  <compose>
    <include>
      <system value="http://hl7.org/fhir/object-role"/>
    </include>
  </compose>


</

ValueSet

>

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.
©
HL7.org
2011+.
FHIR
DSTU2
(v1.0.2-7202)
generated
on
Sat,
Oct
24,
2015
07:42+1100.
Links: