FHIR Cross-Version Extensions package for FHIR R5 from FHIR R4
0.0.1-snapshot-2 - informative International flag

FHIR Cross-Version Extensions package for FHIR R5 from FHIR R4 - Version 0.0.1-snapshot-2. See the Directory of published versions

ValueSet: Cross-version VS for R4.v3.ProvenanceEventCurrentState for use in FHIR R5

Official URL: http://hl7.org/fhir/4.0/ValueSet/R4-v3-ProvenanceEventCurrentState-for-R5 Version: 0.0.1-snapshot-2
Standards status: Informative Maturity Level: 0 Computable Name: R4_v3_ProvenanceEventCurrentState_for_R5

This cross-version ValueSet represents concepts from http://terminology.hl7.org/ValueSet/v3-ProvenanceEventCurrentState 2014-08-07 for use in FHIR R5. Concepts not present here have direct equivalent mappings crossing all versions from R4 to R5.

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

This value set includes codes based on the following rules:

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-ActStatus version 2018-08-12
    CodeDisplayDefinition
    abortedabortedThe Act has been terminated prior to the originally intended completion.
    cancelledcancelledThe Act has been abandoned before activation.
    completedcompletedAn Act that has terminated normally after all of its constituents have been performed.
    newnewAn Act that is in the preparatory stages and may not yet be acted upon
    nullifiednullifiedThis Act instance was created in error and has been 'removed' and is treated as though it never existed. A record is retained for audit purposes only.
    obsoleteobsoleteThis Act instance has been replaced by a new instance.
  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-DocumentCompletion version 2018-08-12
    CodeDisplayDefinition
    AU authenticated A completion status in which a document has been signed manually or electronically by one or more individuals who attest to its accuracy. No explicit determination is made that the assigned individual has performed the authentication. While the standard allows multiple instances of authentication, it would be typical to have a single instance of authentication, usually by the assigned individual.
    DI dictated A completion status in which information has been orally recorded but not yet transcribed.
    DO documented A completion status in which document content, other than dictation, has been received but has not been translated into the final electronic format. Examples include paper documents, whether hand-written or typewritten, and intermediate electronic forms, such as voice to text.
    LA legally authenticated A completion status in which a document has been signed manually or electronically by the individual who is legally responsible for that document. This is the most mature state in the workflow progression.
    UC unsigned completed document A completion status where the document is complete and there is no expectation that the document will be signed.

 

Expansion

This value set expansion contains 11 concepts.

CodeSystemDisplayDefinition
  abortedhttp://terminology.hl7.org/CodeSystem/v3-ActStatusabortedThe Act has been terminated prior to the originally intended completion.
  cancelledhttp://terminology.hl7.org/CodeSystem/v3-ActStatuscancelledThe Act has been abandoned before activation.
  completedhttp://terminology.hl7.org/CodeSystem/v3-ActStatuscompletedAn Act that has terminated normally after all of its constituents have been performed.
  newhttp://terminology.hl7.org/CodeSystem/v3-ActStatusnewAn Act that is in the preparatory stages and may not yet be acted upon
  nullifiedhttp://terminology.hl7.org/CodeSystem/v3-ActStatusnullifiedThis Act instance was created in error and has been 'removed' and is treated as though it never existed. A record is retained for audit purposes only.
  obsoletehttp://terminology.hl7.org/CodeSystem/v3-ActStatusobsoleteThis Act instance has been replaced by a new instance.
  AUhttp://terminology.hl7.org/CodeSystem/v3-DocumentCompletionauthenticatedA completion status in which a document has been signed manually or electronically by one or more individuals who attest to its accuracy. No explicit determination is made that the assigned individual has performed the authentication. While the standard allows multiple instances of authentication, it would be typical to have a single instance of authentication, usually by the assigned individual.
  DIhttp://terminology.hl7.org/CodeSystem/v3-DocumentCompletiondictatedA completion status in which information has been orally recorded but not yet transcribed.
  DOhttp://terminology.hl7.org/CodeSystem/v3-DocumentCompletiondocumentedA completion status in which document content, other than dictation, has been received but has not been translated into the final electronic format. Examples include paper documents, whether hand-written or typewritten, and intermediate electronic forms, such as voice to text.
  LAhttp://terminology.hl7.org/CodeSystem/v3-DocumentCompletionlegally authenticatedA completion status in which a document has been signed manually or electronically by the individual who is legally responsible for that document. This is the most mature state in the workflow progression.
  UChttp://terminology.hl7.org/CodeSystem/v3-DocumentCompletionunsigned completed documentA completion status where the document is complete and there is no expectation that the document will be signed.

Explanation of the columns that may appear on this page:

Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance)
Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code