# Clinical Note Document

26.0.0 AU

Clinical Note Document - Local Development build (v26.0.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

## ValueSet: Information Recipient Type

Official URL: http://digitalhealth.gov.au/fhir/cnd/ValueSet/information-recipient-type-vs | Version: 26.0.0
Active as of 2026-06-19 | Computable Name: InformationRecipientTypeVS
Copyright/Legal: This content is licensed under a Creative Commons Attribution 4.0 International License. See https://creativecommons.org/licenses/by/4.0/

Subset of codes from v3-ParticipationType for use as Clinical Document Information Recipient codes.

This value set defines the permitted codes for identifying information recipients in a Clinical Note Document, ensuring consistent representation of primary, secondary, and tracking recipient roles for clinical note routing and attribution between healthcare providers.

References

- CND Composition

### Logical Definition (CLD)

- Include these codes as defined in `http://terminology.hl7.org/CodeSystem/v3-ParticipationType` version 📍6.0.0

  Code | Display | Definition | English (Australia) (English (Australia), en)
  IRCP | information 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. | information recipient
  PRCP | primary 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. | primary information recipient
  TRC | tracker | A secondary information recipient, who receives copies (e.g., a primary care provider receiving copies of results as ordered by specialist). | tracker

### Expansion

Expansion performed internally based on codesystem ParticipationType v6.0.0 (CodeSystem)

This value set contains 3 concepts

System | Code | Display (en) | Definition | JSON | XML
`http://terminology.hl7.org/CodeSystem/v3-ParticipationType` | IRCP | information 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. |  |
`http://terminology.hl7.org/CodeSystem/v3-ParticipationType` | PRCP | primary 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. |  |
`http://terminology.hl7.org/CodeSystem/v3-ParticipationType` | TRC | tracker | 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