R4 Ballot #2 (Mixed Normative/Trial use)

This page is part of the FHIR Specification (v3.5.0: R4 Ballot #2). 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: R4B R4 R3

4.3.13.204 Code System http://terminology.hl7.org/CodeSystem/coverage-copay-type

Financial Management Work Group Maturity Level: 1Draft Use Context: Not Intended for Production use

This is a code system defined by the FHIR project.

Summary

Defining URL:http://terminology.hl7.org/CodeSystem/coverage-copay-type
Version:3.5.0
Name:ContractTypeCodes
Title:Contract Type Codes
Definition:

This value set includes sample Contract Type codes.

Committee:Financial Management Work Group
OID:2.16.840.1.113883.4.642.1.1149 (for OID based terminology systems)
Copyright:This is an example set.
Source ResourceXML / JSON

This Code system is used in the following value sets:

4.3.13.204.1 Content

4.3.13.204.2 Contract Type Codes

This value set includes sample Contract Type codes.

Copyright Statement: This is an example set.

This code system http://terminology.hl7.org/CodeSystem/coverage-copay-type defines the following codes:

CodeDisplayDefinition
privacy PrivacyPrivacy policy.
disclosure DisclosureInformation disclosure policy.
healthinsurance Health InsuranceHealth Insurance policy.
supply Supply ContractContract to supply goods or services.
consent ConsentConsent Directive.

 

See the full registry of code systems defined as part of FHIR.

Explanation of the columns that may appear on this page:

LvlA few code lists that FHIR defines are hierarchical - each code is assigned a level. See Code System for further information.
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
DisplayThe 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
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code