Clinical Document Architecture with Australian Schema
1.0.0 - current
Clinical Document Architecture with Australian Schema - Local Development build (v1.0.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
Official URL: http://ns.electronichealth.net.au/cda/ValueSet/dh-entitynameuse | Version: 1.0.0 | |||
Draft as of 2024-08-29 | Computable Name: entitynameuse |
Extended Entity Name Use code value set with Organisation Name Use Value from AS 4846-2006 Organisation Name Usage
References
Generated Narrative: ValueSet dh-entitynameuse
This value set includes codes based on the following rules:
Generated Narrative: ValueSet
Expansion based on:
This value set contains 32 concepts
Code | System | Display | Inactive | Definition |
_NameRepresentationUse | http://terminology.hl7.org/CodeSystem/v3-EntityNameUse | NameRepresentationUse | Identifies the different representations of a name. The representation may affect how the name is used. (E.g. use of Ideographic for formal communications.) | |
ABC | http://terminology.hl7.org/CodeSystem/v3-EntityNameUse | Alphabetic | Alphabetic transcription of name (Japanese: romaji) | |
IDE | http://terminology.hl7.org/CodeSystem/v3-EntityNameUse | Ideographic | Ideographic representation of name (e.g., Japanese kanji, Chinese characters) | |
SYL | http://terminology.hl7.org/CodeSystem/v3-EntityNameUse | Syllabic | Syllabic transcription of name (e.g., Japanese kana, Korean hangul) | |
ASGN | http://terminology.hl7.org/CodeSystem/v3-EntityNameUse | assigned | A name assigned to a person. Reasons some organizations assign alternate names may include not knowing the person's name, or to maintain anonymity. Some, but not necessarily all, of the name types that people call "alias" may fit into this category. | |
C | http://terminology.hl7.org/CodeSystem/v3-EntityNameUse | License | As recorded on a license, record, certificate, etc. (only if different from legal name) | |
I | http://terminology.hl7.org/CodeSystem/v3-EntityNameUse | Indigenous/Tribal | e.g. Chief Red Cloud | |
L | http://terminology.hl7.org/CodeSystem/v3-EntityNameUse | Legal | Known as/conventional/the one you use | |
OR | http://terminology.hl7.org/CodeSystem/v3-EntityNameUse | official registry | **Definition:**The formal name as registered in an official (government) registry, but which name might not be commonly used. Particularly used in countries with a law system based on Napoleonic law. | |
P | http://terminology.hl7.org/CodeSystem/v3-EntityNameUse | pseudonym | A self asserted name that the person is using or has used. | |
A | http://terminology.hl7.org/CodeSystem/v3-EntityNameUse | Artist/Stage | Includes writer's pseudonym, stage name, etc | |
R | http://terminology.hl7.org/CodeSystem/v3-EntityNameUse | Religious | e.g. Sister Mary Francis, Brother John | |
SRCH | http://terminology.hl7.org/CodeSystem/v3-EntityNameUse | search | A name intended for use in searching or matching. | |
PHON | http://terminology.hl7.org/CodeSystem/v3-EntityNameUse | phonetic | A name spelled phonetically. There are a variety of phonetic spelling algorithms. This code value does not distinguish between these.Discussion: | |
SNDX | http://terminology.hl7.org/CodeSystem/v3-EntityNameUse | Soundex | A name spelled according to the SoundEx algorithm. | |
_EntityNameSearchUse | http://terminology.hl7.org/CodeSystem/v3-EntityNameUse | EntityNameSearchUse | inactive | Description: A name intended for use in searching or matching. |
_OrganizationNameUse | http://terminology.hl7.org/CodeSystem/v3-EntityNameUse | OrganizationNameUse | inactive | |
_PersonNameUse | http://terminology.hl7.org/CodeSystem/v3-EntityNameUse | PersonNameUse | inactive | A code indicating the type of name (e.g. nickname, alias, maiden name, legal, adopted) |
T | http://ns.electronichealth.net.au/cda/CodeSystem/dh-entitynameuse | |||
DN | http://ns.electronichealth.net.au/cda/CodeSystem/dh-entitynameuse | |||
M | http://ns.electronichealth.net.au/cda/CodeSystem/dh-entitynameuse | |||
NB | http://ns.electronichealth.net.au/cda/CodeSystem/dh-entitynameuse | |||
UI | http://ns.electronichealth.net.au/cda/CodeSystem/dh-entitynameuse | |||
SP | http://ns.electronichealth.net.au/cda/CodeSystem/dh-entitynameuse | |||
ORGU | http://ns.electronichealth.net.au/cda/CodeSystem/dh-entitynameuse | |||
ORGS | http://ns.electronichealth.net.au/cda/CodeSystem/dh-entitynameuse | |||
ORGB | http://ns.electronichealth.net.au/cda/CodeSystem/dh-entitynameuse | |||
ORGL | http://ns.electronichealth.net.au/cda/CodeSystem/dh-entitynameuse | |||
ORGA | http://ns.electronichealth.net.au/cda/CodeSystem/dh-entitynameuse | |||
ORGE | http://ns.electronichealth.net.au/cda/CodeSystem/dh-entitynameuse | |||
ORGX | http://ns.electronichealth.net.au/cda/CodeSystem/dh-entitynameuse | |||
ORGY | http://ns.electronichealth.net.au/cda/CodeSystem/dh-entitynameuse |
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 |