Extensions for Using Data Elements from FHIR R5 in FHIR R4
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR R5 in FHIR R4 - Downloaded Version null See the Directory of published versions

ValueSet: R5V3XActClassDocumentEntryActForR4

Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R5-v3-xActClassDocumentEntryAct-for-R4 Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: R5V3XActClassDocumentEntryActForR4

This cross-version ValueSet represents content from http://terminology.hl7.org/ValueSet/v3-xActClassDocumentEntryAct|2.0.0 for use in FHIR R4.

This value set is part of the cross-version definitions generated to enable use of the value set http://terminology.hl7.org/ValueSet/v3-xActClassDocumentEntryAct|2.0.0 as defined in FHIR R5 in FHIR R4.

The source value set is bound to the following FHIR R5 elements:

Note that all concepts are included in this cross-version definition because no concepts have compatible representations

Following are the generation technical comments:

FHIR ValueSet http://terminology.hl7.org/ValueSet/v3-xActClassDocumentEntryAct|2.0.0, defined in FHIR R5 does not have any mapping to FHIR R4

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)

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-ActClass version 📍3.1.1
    CodeDisplay
    ACCMaccommodation
    ACSNaccession
    ACTact
    AEXPOSacquisition exposure
    CONSconsent
    CONTREGcontainer registration
    CTTEVENTclinical trial timepoint event
    DISPACTdisciplinary action
    EXPOSexposure
    INCincident
    INFRMinform
    LISTworking list
    MPROTmonitoring program
    PCPRcare provision
    REGregistration
    REVreview
    SPCTRTspecimen treatment
    STOREstorage
    TEXPOStransmission exposure
    TRFRtransfer
    TRNStransportation

 

Expansion

This value set expansion contains 21 concepts.

SystemVersionCodeDisplayJSONXML
http://terminology.hl7.org/CodeSystem/v3-ActClass3.1.1  ACCMaccommodation
http://terminology.hl7.org/CodeSystem/v3-ActClass3.1.1  ACSNaccession
http://terminology.hl7.org/CodeSystem/v3-ActClass3.1.1  ACTact
http://terminology.hl7.org/CodeSystem/v3-ActClass3.1.1  AEXPOSacquisition exposure
http://terminology.hl7.org/CodeSystem/v3-ActClass3.1.1  CONSconsent
http://terminology.hl7.org/CodeSystem/v3-ActClass3.1.1  CONTREGcontainer registration
http://terminology.hl7.org/CodeSystem/v3-ActClass3.1.1  CTTEVENTclinical trial timepoint event
http://terminology.hl7.org/CodeSystem/v3-ActClass3.1.1  DISPACTdisciplinary action
http://terminology.hl7.org/CodeSystem/v3-ActClass3.1.1  EXPOSexposure
http://terminology.hl7.org/CodeSystem/v3-ActClass3.1.1  INCincident
http://terminology.hl7.org/CodeSystem/v3-ActClass3.1.1  INFRMinform
http://terminology.hl7.org/CodeSystem/v3-ActClass3.1.1  LISTworking list
http://terminology.hl7.org/CodeSystem/v3-ActClass3.1.1  MPROTmonitoring program
http://terminology.hl7.org/CodeSystem/v3-ActClass3.1.1  PCPRcare provision
http://terminology.hl7.org/CodeSystem/v3-ActClass3.1.1  REGregistration
http://terminology.hl7.org/CodeSystem/v3-ActClass3.1.1  REVreview
http://terminology.hl7.org/CodeSystem/v3-ActClass3.1.1  SPCTRTspecimen treatment
http://terminology.hl7.org/CodeSystem/v3-ActClass3.1.1  STOREstorage
http://terminology.hl7.org/CodeSystem/v3-ActClass3.1.1  TEXPOStransmission exposure
http://terminology.hl7.org/CodeSystem/v3-ActClass3.1.1  TRFRtransfer
http://terminology.hl7.org/CodeSystem/v3-ActClass3.1.1  TRNStransportation

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