This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions
Financial Management Work Group | Maturity Level: 1 | Draft | Use Context: Country: World, Not Intended for Production use |
Official URL: http://hl7.org/fhir/ValueSet/datestype
|
Version: 6.0.0-ballot2 | |||
draft as of 2024-11-20 | Computable Name: DatesTypeCodes | |||
Flags: Experimental | OID: |
This value set is used in the following places:
This value set includes sample Dates Type codes.
Generated Narrative: ValueSet datestype
Last updated: 2024-11-20T21:23:48.918Z
Profile: Shareable ValueSet
http://hl7.org/fhir/datestype
This expansion generated 20 Nov 2024
Generated Narrative: ValueSet
Last updated: 2024-11-20T21:23:48.918Z
Profile: Shareable ValueSet
Expansion based on codesystem Dates Event Type Codes v6.0.0-ballot2 (CodeSystem)
This value set contains 3 concepts
Code | System | Display | Definition |
card-issued | http://hl7.org/fhir/datestype | Card Issued | The date when an insurance card was issued. |
claim-received | http://hl7.org/fhir/datestype | Claim Received | The date when an insurer nreceived a claim, pre-authorization or predetermination. |
service-expected | http://hl7.org/fhir/datestype | Service Expected | The date or period on or during which the services are expected to be performed. |
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 |