This page is part of the FHIR Specification (v5.0.0-draft-final: Final QA Preview for R5 - see ballot notes). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3
Financial Management Work Group | Maturity Level: 1 | Draft | Use Context: Country: World, Not Intended for Production use |
Official URL: http://hl7.org/fhir/ValueSet/claim-subtype
|
Version: 5.0.0-draft-final | |||
draft as of 2023-03-01 | Computable Name: ExampleClaimSubTypeCodes | |||
Flags: Experimental | OID: 2.16.840.1.113883.4.642.3.566 |
This value set is used in the following places:
This value set includes sample Claim SubType codes which are used to distinguish the claim types for example within type institutional there may be subtypes for emergency services, bed stay and transportation.
http://terminology.hl7.org/CodeSystem/ex-claimsubtype
This expansion generated 01 Mar 2023
This value set contains 2 concepts
Expansion based on Example Claim SubType Codes v0.1.0 (CodeSystem)
Code | System | Display | Definition |
ortho | http://terminology.hl7.org/CodeSystem/ex-claimsubtype | Orthodontic Claim | A claim for Orthodontic Services. |
emergency | http://terminology.hl7.org/CodeSystem/ex-claimsubtype | Emergency Claim | A claim for emergency services. |
See the full registry of value sets defined as part of FHIR.
Explanation of the columns that may appear on this page:
Lvl | A few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information |
Source | 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). If the code is in italics, this indicates that the code is not selectable ('Abstract') |
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 |