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

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

ValueSet: R3V3ParticipationInformationGeneratorForR5

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

This cross-version ValueSet represents content from http://hl7.org/fhir/ValueSet/v3-ParticipationInformationGenerator|2014-03-26 for use in FHIR R5.

This value set is part of the cross-version definitions generated to enable use of the value set http://hl7.org/fhir/ValueSet/v3-ParticipationInformationGenerator|2014-03-26 as defined in FHIR STU3 in FHIR R5.

The source value set is bound to the following FHIR STU3 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://hl7.org/fhir/ValueSet/v3-ParticipationInformationGenerator|2014-03-26, defined in FHIR STU3 does not have any mapping to FHIR 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)

  • Include these codes as defined in http://hl7.org/fhir/v3/ParticipationType version 📍2016-11-11
    CodeDisplayDefinition
    AUTauthor (originator)Definition: A party that originates the Act and therefore has responsibility for the information given in the Act and ownership of this Act.


    Example: the report writer, the person writing the act definition, the guideline author, the placer of an order, the EKG cart (device) creating a report etc. Every Act should have an author. Authorship is regardless of mood always actual authorship.

    Examples of such policies might include:



    The author and anyone they explicitly delegate may update the report;



    All administrators within the same clinic may cancel and reschedule appointments created by other administrators within that clinic;



    A party that is neither an author nor a party who is extended authorship maintenance rights by policy, may only amend, reverse, override, replace, or follow up in other ways on this Act, whereby the Act remains intact and is linked to another Act authored by that other party.
    ENTdata entry personA person entering the data into the originating system. The data entry person is collected optionally for internal quality control purposes. This includes the transcriptionist for dictated text.
    INFinformantA source of reported information (e.g., a next of kin who answers questions about the patient's history). For history questions, the patient is logically an informant, yet the informant of history questions is implicitly the subject.
    TRANSTranscriberAn entity entering the data into the originating system. The data entry entity is collected optionally for internal quality control purposes. This includes the transcriptionist for dictated text transcribed into electronic form.
    WITwitnessOnly with service events. A person witnessing the action happening without doing anything. A witness is not necessarily aware, much less approves of anything stated in the service event. Example for a witness is students watching an operation or an advanced directive witness.

 

Expansion

This value set expansion contains 5 concepts.

SystemVersionCodeDisplayDefinitionJSONXML
http://hl7.org/fhir/v3/ParticipationType2016-11-11  AUTauthor (originator)

Definition: A party that originates the Act and therefore has responsibility for the information given in the Act and ownership of this Act.

                       Example: the report writer, the person writing the act definition, the guideline author, the placer of an order, the EKG cart (device) creating a report etc. Every Act should have an author. Authorship is regardless of mood always actual authorship. 

                    Examples of such policies might include:

                    
                       
                          The author and anyone they explicitly delegate may update the report;

                       
                       
                          All administrators within the same clinic may cancel and reschedule appointments created by other administrators within that clinic;

                       
                    
                    A party that is neither an author nor a party who is extended authorship maintenance rights by policy, may only amend, reverse, override, replace, or follow up in other ways on this Act, whereby the Act remains intact and is linked to another Act authored by that other party.
http://hl7.org/fhir/v3/ParticipationType2016-11-11  ENTdata entry person

A person entering the data into the originating system. The data entry person is collected optionally for internal quality control purposes. This includes the transcriptionist for dictated text.

http://hl7.org/fhir/v3/ParticipationType2016-11-11  INFinformant

A source of reported information (e.g., a next of kin who answers questions about the patient's history). For history questions, the patient is logically an informant, yet the informant of history questions is implicitly the subject.

http://hl7.org/fhir/v3/ParticipationType2016-11-11  TRANSTranscriber

An entity entering the data into the originating system. The data entry entity is collected optionally for internal quality control purposes. This includes the transcriptionist for dictated text transcribed into electronic form.

http://hl7.org/fhir/v3/ParticipationType2016-11-11  WITwitness

Only with service events. A person witnessing the action happening without doing anything. A witness is not necessarily aware, much less approves of anything stated in the service event. Example for a witness is students watching an operation or an advanced directive witness.


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