FHIR Release 3 (STU) 5 Ballot

This page is part of the FHIR Specification (v3.0.2: STU (v5.0.0-ballot: R5 Ballot - see ballot notes 3). ). 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: R5 R4B R4 R3 R2

Codesystem-contract-content-derivative.xml

Example DetectedIssue/lab (XML)

Vocabulary Clinical Decision Support Work Group Maturity Level : N/A Ballot Standards Status : Informative Compartments : Device , Patient , Practitioner

Raw XML ( canonical form + also see XML Format Specification )

Jump past Narrative

Definition for Code System Contract Content Derivation Codes Lab order is contraindicated based on a patient's existing medication (id = "lab")

<?xml version="1.0" encoding="UTF-8"?>

<DetectedIssue xmlns="http://hl7.org/fhir">
  <id value="lab"/> 
  <text> 
    <status value="generated"/> 
    This is an example set of Content Derivative type
      codes, which represent the minimal content derived from the basal information source
       at a
      specific stage in its lifecycle, which is sufficient to manage that source information,
       for
      example, in a repository, registry, processes and workflows, for making access control
      decisions, and providing query responses.
      
      
      
        This is an example set of Content Derivative type codes, which represent the minimal content
           derived from the basal information source at a specific stage in its lifecycle, which
           is sufficient to manage that source information, for example, in a repository, registry,
           processes and workflows, for making access control decisions, and providing query responses.

    <div xmlns="http://www.w3.org/1999/xhtml">[Put rendering here]</div> 
  </text> 

      
      
         This is an example set.
      
      This code system http://hl7.org/fhir/contract-content-derivative defines the following
         codes:
      
        
          
            
          
          
            
          
          
            
          
        
        
          registration
            
          
          
          Content derivative that conveys sufficient information needed to register the source basal
             content from which it is derived.  This derivative content may be used to register the
             basal content as it changes status in its lifecycle.  For example, content registration
             may occur when the basal content is created, updated, inactive, or deleted.
        
        
          retrieval
            
          
          
          
        
        
          statement
            
          
          
          Content derivative that has less than full fidelity to the basal information source from
             which it was 'transcribed'. It provides recipients with the full content representation
             they may require for compliance purposes, and typically include a reference to or an attached
             unstructured representation for recipients needing an exact copy of the legal agreement.
        
        
          shareable
            
          
          
          A Content Derivative that conveys sufficient information to determine the authorized entities
             with which the content may be shared.
        
      
    
  
  
    
  
  
    
  
  
    
  
  
  
    
    
  
  
  
  
  
  
  
    
    
      
      
    
  
  
    
      
      
    
  
  This is an example set of Content Derivative type codes, which represent the minimal content
   derived from the basal information source at a specific stage in its lifecycle, which
   is sufficient to manage that source information, for example, in a repository, registry,
   processes and workflows, for making access control decisions, and providing query responses.
  
  
  
  
  
    
    
    Content derivative that conveys sufficient information needed to register the source basal
     content from which it is derived.  This derivative content may be used to register the
     basal content as it changes status in its lifecycle.  For example, content registration
     may occur when the basal content is created, updated, inactive, or deleted.
  
  
    
    
    
  
  
    
    
    Content derivative that has less than full fidelity to the basal information source from
     which it was 'transcribed'. It provides recipients with the full content representation
     they may require for compliance purposes, and typically include a reference to or an attached
     unstructured representation for recipients needing an exact copy of the legal agreement.
  
  
    
    
    A Content Derivative that conveys sufficient information to determine the authorized entities
     with which the content may be shared.
  

  <!--   insert contents here   -->
  <status value="final"/> 


</
CodeSystem


DetectedIssue


>



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.