This cross-version profile on the R5.Basic resource can be used to represent a FHIR R4B.CatalogEntry resource.

This cross-version profile on the R5.Basic resource can be used to represent a FHIR R4B.DocumentManifest resource.

This cross-version profile on the R5.Basic resource can be used to represent a FHIR R4B.Population resource.

This cross-version profile on the R5.Basic resource can be used to represent a FHIR R4B.ProdCharacteristic resource.

This cross-version profile on the R5.Basic resource can be used to represent a FHIR R4B.ResearchDefinition resource.

This cross-version profile on the R5.Basic resource can be used to represent a FHIR R4B.ResearchElementDefinition resource.

Preferred value set for Condition Categories.

This is an example code system that includes all the ACME codes for serum/plasma cholesterol from v2.36.

A list of the base types defined by this version of the FHIR specification - types that are defined, but for which only specializations actually are created.

Indicates whether the account is available to be used.

Defines behavior for an action or a group for how many times that item may be repeated.

Provides examples of actions to be performed.

Defines the kinds of conditions that can appear on actions.

Defines organization behavior of a group.

The type of participant for the action.

Defines selection frequency behavior for an action or group.

Provides examples of reasons for actions to be performed.

Defines the types of relationships between actions.

Defines expectations around whether an action or action group is required.

Defines selection behavior of a group.

The type of action to be performed.

Extra monitoring defined for a Medicinal Product.

The type of an address (physical / postal).

The use of an address.

This value set includes a smattering of Adjudication codes.

This value set includes a smattering of adjudication codes.

This value set includes smattering of Adjudication Reason codes.

Dose form for a medication, in the form suitable for administering to the patient, after mixing, where necessary.

The gender of a person used for administrative purposes.

This codesystem defines a set of codes that can be used to indicate from where the patient came in.

Overall nature of the adverse event, e.g. real or potential.

Overall categorization of the event, e.g. product-related or situational.

Codes for the assessment of whether the entity caused the event.

TODO.

TODO (and should this be required?).

Overall seriousness of this event for the patient.

The severity of the adverse event itself, in direct relation to the subject.

How resource references can be aggregated.

Preferred value set for AllergyIntolerance Clinical Status.

Preferred value set for AllergyIntolerance Verification Status.

Category of an identified substance associated with allergies or intolerances.

Statement about the degree of clinical certainty that a specific substance was the cause of the manifestation in a reaction event.

Estimate of the potential clinical harm, or seriousness, of a reaction to an identified substance.

Clinical assessment of the severity of a reaction event as a whole, potentially considering multiple different manifestations.

Identification of the underlying physiological mechanism for a Reaction Risk.

This example value set defines a set of codes that can be used to indicate species of animal patients.

A tissue type of an animal.

The free/busy status of an appointment.

Code the reason for different URLs, eg abstract and full-text.

Artifact Contribution Instance Type

Citation contribution.

Artifact Relationship Type

The type of direction to use for assertion.

The type of operator to use for assertion.

The type of response code to use for assertion.

A statistic about a statistic, e.g. Confidence interval or p-value

Event Types for Audit Events - defined by DICOM with some FHIR specific additions.

The type of process where the audit event originated from.

Indicator for type of action performed during the event that generated the event.

The type of network access point of this agent in the audit event.

Code representing the role the entity played in the audit event.

Code for the entity type involved in the audit event (derived from ATNA).

Indicates whether the event succeeded or failed.

This value set defines codes for resources not yet supported by (or which will never be supported by) FHIR. Many of the codes listed here will eventually be turned into official resources. However, there is no guarantee that any particular resource will be created nor that the scope will be exactly as defined by the codes presented here. Codes in this set will be deprecated if/when formal resources are defined that encompass these concepts.

This value set includes the Patient to subscriber relationship codes.

This value set includes a smattering of Benefit SubCategory codes.

This value set includes a smattering of Benefit Term codes.

This value set includes a smattering of Benefit type codes.

Whether the cost applies to in-network or out-of-network providers.

Indication of the degree of conformance expectations associated with a binding.

Biologically Derived Product Category.

Biologically Derived Product Status.

BiologicallyDerived Product Storage Scale.

Indicates the purpose of a bundle - how it is intended to be used.

The master set of status codes used throughout FHIR. All status codes are mapped to one of these codes.

How a capability statement is intended to be used.

Codes that reflect the current state of a care plan activity within its overall life cycle.

Indicates the status of the care team.

The type of relations between entries.

Logical grouping of characteristics.

The method used to determine the characteristic(s) of the variable.

Example set of codes that can be used for billing purposes.

Codes identifying the lifecycle stage of a ChargeItem.

Citation artifact classifier

Citation classification type

Citation status type

The format for display of the citation.

Used to express the reason and specific aspect for the variant abstract, such as language and specific language

Cited Artifact Classification Type

To describe the reason for the variant citation, such as version number or subpart specification.

Cited Artifact Status Type

NLM codes Internet or Print.

This value set includes sample Claim Care Team Role codes.

This value set includes sample Information Category codes.

This value set includes sample Payee Type codes.

This value set includes Claim Type codes.

Overall defining type of this clinical use definition.

This is an example code system summary for the ACME codes for body site.

The degree to which the server supports the code search parameter on ValueSet, if it is supported.

The extent of the content of the code system (the concepts and codes it defines) are represented in a code system resource.

The meaning of the hierarchy of concepts in a code system.

Dose forms for a product as a whole, considering all individual parts, but before any mixing

Common Tag Codes defined by FHIR project

Codes for general categories of communications such as alerts, instructions, etc.

Codes for the reason why a communication did not happen.

Codes describing the purpose or content of the communication.

Which type a compartment definition describes.

The composite scoring method of the measure.

The way in which a person authenticated a composition.

The workflow/clinical status of the composition.

Codes indicating the results of a subsumption check between codes

The degree of equivalence between concepts.

Defines which action to take if there is no match in the group.

Example value set for Condition Categories.

Preferred value set for Condition Clinical Status.

The verification status to support or decline the clinical status of the condition or diagnosis.

A code that indicates how the server supports conditional delete.

A code that indicates how the server supports conditional read.

This value set includes example Consent Action codes.

FHIR Specific Example codes for Consent Category

This value set includes the current scopes for the Consent resources.

How a resource reference is interpreted when testing consent restrictions.

How a rule statement is applied, such as adding additional consent or removing consent.

Indicates the state of the consent.

SHALL applications comply with this constraint?

This example value set defines a set of codes that can be used to indicate the purpose for which you would contact a contact party.

Telecommunications form for contact point.

Use of contact point.

Color of the container cap.

This value set includes sample Contract Action codes.

This value set includes sample Contract Actor Role codes.

This value set includes sample Contract Signer Type codes.

This value set includes sample Contract Subtype codes.

This value set includes sample Contract Term SubType codes.

This value set includes sample Contract Term Type codes.

This value set includes sample Contract Type codes.

This CodeSystem contains FHIR-defined contract action status types.

This CodeSystem contains FHIR-defined contract asset availability types.

This CodeSystem contains FHIR-defined contract asset context types.

This CodeSystem contains FHIR-defined contract asset scope types.

This CodeSystem contains FHIR-defined contract asset type sub-types.

This CodeSystem contains FHIR-defined contract asset type types.

This is an example set of Content Derivative type codes, which represent the minimal content derived from the basal information source at a specific stage in its lifecycle, which is sufficient to manage that source information, for example, in a repository, registry, processes and workflows, for making access control decisions, and providing query responses.

This CodeSystem contains FHIR-defined contract decision mode types.

This CodeSystem contains FHIR-defined contract definition subtypes.

This CodeSystem contains FHIR-defined contract definition types.

This CodeSystem contains FHIR-defined contract Expiration types.

This CodeSystem contains FHIR-defined contract status types. Each definition includes usage notes explaining the precedence order in contract lifecycle - i.e., while only some stages are required, the order in which they may occur is deterministic; and a map to comparable FHIR and v.3 status codes. It follows guidance about use of status codes in FHIR at http://build.fhir.org/sc.html.

This CodeSystem contains FHIR-defined contract party role types.

This CodeSystem contains FHIR-defined contract publication status types. Each definition includes usage notes explaining the precedence order in contract publication lifecycle - i.e., while only some stages are required, the order in which they may occur is deterministic.

This CodeSystem contains FHIR-defined contract Expiration types.

This CodeSystem contains FHIR-defined contract security category types.

This CodeSystem contains FHIR-defined contract security classification types.

This CodeSystem contains FHIR-defined contract security control types.

This CodeSystem contains FHIR-defined contract status types. Each definition includes usage notes explaining the precedence order in contract lifecycle - i.e., while only some stages are required, the order in which they may occur is deterministic; and a map to comparable FHIR and v.3 status codes. It follows guidance about use of status codes in FHIR at http://build.fhir.org/sc.html.

Used to code the format of the display string.

Used to code the producer or rule for creating the display string.

Used to code the format of the display string.

Used to code author list statement, contributorship statement, and such.

The type of contributor.

This value set includes Coverage Class codes.

This codeset includes Coverage Copayment Type codes.

This value set includes CoverageEligibilityResponse Auth Support codes.

Behavior a server can exhibit when a criteria state does not exist (e.g., state prior to a create or after a delete).

Attached is vocabulary for the record lifecycle events, as per DICOM Audit Message,

DICOM Code Definitions (Coding Scheme Designator “DCM” Coding Scheme Version “01”)

Used to specify why the normally expected content of the data element is missing.

A version specific list of the data types defined by the FHIR specification for use as an element type (any of the FHIR defined data types).

The days of the week.

A list of all the definition resource types defined in this version of the FHIR specification.

Codes identifying the lifecycle stage of a definition.

High-level categorization of the definition, used for searching, sorting, and filtering.

Preferred value set for Condition Categories.

Indicates the potential degree of impact of the identified issue on the patient.

Describes the state of a metric calibration.

Describes the type of a metric calibration.

Describes the category of the metric.

Describes the typical color of representation.

Describes the operational status of the DeviceMetric.

The type of name the device is referred by.

A coded concept indicating the current status of the Device Usage.

This value set defines a set of codes that can be used to express the role of a diagnosis on the Encounter or EpisodeOfCare record.

The status of the diagnostic report.

This codesystem defines a set of codes that can be used to indicate dietary preferences or restrictions a patient may have.

Codes for high level media types - whether the media is an image, video, or audio.

This codesystem defines a set of codes that can be used to where the patient left the hospital.

How an element value is interpreted when discrimination is evaluated.

Whether the application produces or consumes documents.

The status of the document reference.

The type of relationship between documents.

The kind of dose or rate specified.

A code specifying the types of information being requested.

A code specifying the types of information being requested.

Controls how multiple enableWhen values are interpreted - whether all or any must be true.

The status of the location.

Current state of the encounter.

This example codesystem defines a set of codes that can be used to indicate the type of encounter: a specific code indicating type of service provided.

This is an example codesystem defined by the FHIR project, that could be used to represent possible connection type profile values.

This is an example codesystem defined by the FHIR project, it represents global concepts for no content, or any unrestricted content.

The status of the endpoint.

EnteralFormulaAdditiveType: Codes for the type of modular component such as protein, carbohydrate or fiber to be provided in addition to or mixed with the base formula. This value set is provided as a suggestive example.

The status of the episode of care.

This incomplete example codesystem defines a set of codes that can be used to express the usage type of an EpisodeOfCare record.

The mode of a message capability statement.

A list of all the event resource types defined in this version of the FHIR specification.

Codes identifying the lifecycle stage of an event.

Real world event relating to the schedule.

The assessment of quality, confidence, or certainty.

The aspect of quality, confidence, or certainty.

Commonly used classifiers for evidence sets.

The quality of how direct the match is.

The kind of report, such as grouping of classifiers, search results, or human-compiled expression.

The handling of the variable in statistical analysis for exposures or outcomes (E.g. Dichotomous, Continuous, Descriptive).

The role that the assertion variable plays.

The possible types of variables for exposures or outcomes (E.g. Dichotomous, Continuous, Descriptive).

This value set includes sample Claim SubType codes.

This codeset includes Example Coverage Financial Exceptions Code.

This value set includes sample Diagnosis Related Group codes.