Affiliate Report Implementation Guide
0.1.0 - ci-build
Affiliate Report Implementation Guide, published by HL7 International Council. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/ralych/affiliate-report-ig/ and changes regularly. See the Directory of published versions
| Official URL: http://affiliate-report.acme.hl7.org/ValueSet/affiliate-report-contact-purpose-vs | Version: 0.1.0 | |||
| Draft as of 2024-09-26 | Computable Name: ContactPurposeVs | |||
Contact Purpose ValueSet
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
Generated Narrative: ValueSet
Expansion based on codesystem Affiliate Report Contact Purpose CodeSystem v0.1.0 (CodeSystem)
This value set contains 5 concepts
| Code | System | Display |
| CHAIR | http://affiliate-report.acme.hl7.org/CodeSystem/affiliate-report-contact-purpose-cs | The chair contact |
| VICECHAIR | http://affiliate-report.acme.hl7.org/CodeSystem/affiliate-report-contact-purpose-cs | The vice chair contact |
| TL | http://affiliate-report.acme.hl7.org/CodeSystem/affiliate-report-contact-purpose-cs | The technical lead |
| TM | http://affiliate-report.acme.hl7.org/CodeSystem/affiliate-report-contact-purpose-cs | The technical manager |
| HQ | http://affiliate-report.acme.hl7.org/CodeSystem/affiliate-report-contact-purpose-cs | The headquater contact |
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 |