FHIR Clinical Documents
1.0.0-ballot - STU1 Ballot International flag

FHIR Clinical Documents, published by HL7 International / Structured Documents. This guide is not an authorized publication; it is the continuous build for version 1.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-clinical-document/ and changes regularly. See the Directory of published versions

ValueSet: Clinical Document Participant Types that are information recipients (Experimental)

Official URL: http://hl7.org/fhir/uv/fhir-clinical-document/ValueSet/clinical-doc-information-recipient-vs Version: 1.0.0-ballot
Standards status: Informative Computable Name: ClinicalDocInformationRecipientVs

Copyright/Legal: Used by permission of HL7 International, all rights reserved Creative Commons License

Subset of codes from v3-ParticipationType for use as Clinical Document Participant Type codes, which are specifically CDA information recipients

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)

Generated Narrative: ValueSet clinical-doc-information-recipient-vs

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-ParticipationType
    CodeDisplayDefinition
    IRCPinformation recipientA party, who may or should receive or who has recieved the Act or subsequent or derivative information of that Act. Information recipient is inert, i.e., independent of mood." Rationale: this is a generalization of a too diverse family that the definition can't be any more specific, and the concept is abstract so one of the specializations should be used.
    PRCPprimary information recipientInformation recipient to whom an act statement is primarily directed. E.g., a primary care provider receiving a discharge letter from a hospitalist, a health department receiving information on a suspected case of infectious disease. Multiple of these participations may exist on the same act without requiring that recipients be ranked as primary vs. secondary.
    TRCtrackerA secondary information recipient, who receives copies (e.g., a primary care provider receiving copies of results as ordered by specialist).

 

Expansion

Generated Narrative: ValueSet

Expansion based on codesystem ParticipationType v5.0.0 (CodeSystem)

This value set contains 3 concepts

CodeSystemDisplayDefinition
  IRCPhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeinformation recipient

A party, who may or should receive or who has recieved the Act or subsequent or derivative information of that Act. Information recipient is inert, i.e., independent of mood." Rationale: this is a generalization of a too diverse family that the definition can't be any more specific, and the concept is abstract so one of the specializations should be used.

  PRCPhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeprimary information recipient

Information recipient to whom an act statement is primarily directed. E.g., a primary care provider receiving a discharge letter from a hospitalist, a health department receiving information on a suspected case of infectious disease. Multiple of these participations may exist on the same act without requiring that recipients be ranked as primary vs. secondary.

  TRChttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypetracker

A secondary information recipient, who receives copies (e.g., a primary care provider receiving copies of results as ordered by specialist).

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