Adverse Event Clinical Research R4 Backport
1.0.1 - STU1 International flag

Adverse Event Clinical Research R4 Backport, published by HL7 International / Biomedical Research and Regulation. This guide is not an authorized publication; it is the continuous build for version 1.0.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-ae-research-backport-ig/ and changes regularly. See the Directory of published versions

ValueSet: Adverse Event Participant Functions (Experimental)

Official URL: http://hl7.org/fhir/uv/ae-research-backport-ig/ValueSet/adverse-event-participant-function-vs Version: 1.0.1
Standards status: Informative Computable Name: AdverseEventParticipantFunction

This value set includes codes that describe the type of involvement of the actor in the adverse event.

References

Logical Definition (CLD)

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-ParticipationType
    CodeDisplayDefinition
    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.
    PARTParticipationIndicates that the target of the participation is involved in some manner in the act, but does not qualify how.
    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.
    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.

 

Expansion

Expansion based on codesystem ParticipationType v5.0.0 (CodeSystem)

This value set contains 4 concepts.

CodeSystemDisplayDefinition
  INFhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeinformant

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.

  PARThttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeParticipation

Indicates that the target of the participation is involved in some manner in the act, but does not qualify how.

  WIThttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypewitness

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.

  AUThttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeauthor (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.

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