FHIR Cross-Version Extensions package for FHIR R5 from FHIR R4 - Version 0.0.1-snapshot-2. See the Directory of published versions
| Official URL: http://hl7.org/fhir/4.0/ValueSet/R4-network-type-for-R5 | Version: 0.0.1-snapshot-2 | |||
| Standards status: Informative | Maturity Level: 3 | Responsible: Security | Computable Name: R4_network_type_for_R5 | |
| This cross-version ValueSet represents concepts from http://hl7.org/fhir/ValueSet/network-type | 4.0.1 for use in FHIR R5. Concepts not present here have direct equivalent mappings crossing all versions from R4 to R5. |
References
http://hl7.org/fhir/network-type version 4.0.1| Code | Display | Definition |
| 1 | Machine Name | The machine name, including DNS name. |
| 2 | IP Address | The assigned Internet Protocol (IP) address. |
| 3 | Telephone Number | The assigned telephone number. |
| 4 | Email address | The assigned email address. |
| 5 | URI | URI (User directory, HTTP-PUT, ftp, etc.). |
This value set expansion contains 5 concepts.
| Code | System | Display | Definition |
| 1 | http://hl7.org/fhir/network-type | Machine Name | The machine name, including DNS name. |
| 2 | http://hl7.org/fhir/network-type | IP Address | The assigned Internet Protocol (IP) address. |
| 3 | http://hl7.org/fhir/network-type | Telephone Number | The assigned telephone number. |
| 4 | http://hl7.org/fhir/network-type | Email address | The assigned email address. |
| 5 | http://hl7.org/fhir/network-type | URI | URI (User directory, HTTP-PUT, ftp, etc.). |
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 |