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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

This cross-version profile on the R4.Basic resource can be used to represent a FHIR R4B.SubstanceDefinition 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.

This value set includes example Diagnosis Type codes.

This value set includes example Diagnosis on admission codes.

Example Message Reasons. These are the set of codes that might be used an updating an encounter using admin-update.

This value set includes example Procedure Type codes.

This value set includes sample Program reason codes.

This value set includes sample Provider Qualification codes.

This value set includes sample Related Claim Relationship codes.

This value set includes sample Revenue Center codes.

This value set includes a smattering of Service Place codes.

Example use codes for the List resource - typical kinds of use.

This value set includes a smattering of Prescription Product codes.

The type of actor - system or human.

This value set includes sample Exception codes.

A code specifying the state of the resource instance.

The media type of the expression language.

How an extension context is interpreted.

This value set includes coded concepts not well covered in any of the included valuesets.

A set of common concept properties for use on coded systems throughout the FHIR eco-system.

The set of interactions defined by the RESTful part of the FHIR specification.

The availability status of the device.

The availability status reason of the device.

All FHIRPath data types

A code to indicate if the substance is actively used.

All published FHIR Versions.

Codes describing the reason why a family member’s history is not available.

A code that identifies the status of the family history record.

Materials used or needed to feed the patient. These values are provided as a suggestive example.

The kind of operation to perform as a part of a property based filter.

This value set includes Status codes.

Example list of detail codes for flagged issues. (Not complete or necessarily appropriate.)

This value set is provided as an exemplar. The value set is driven by IHE Table B.8-4: Abnormal Flags, Alert Priority.

Indicates whether this flag is active and needs to be displayed to a user, or whether it is no longer needed or was entered in error.

Evidence focus characteristic code.

This value set includes a sample set of Forms codes.

This value set includes sample funds reservation type codes.

This example code System defines a set of codes that can be used to indicate a patient’s gender identity.

This example value set defines a set of codes that can be used to indicate the current state of the animal’s reproductive organs.

Codes to denote a guideline or policy statement.when a genetic test result is being shared as a secondary finding.

Describes the progression, or lack thereof, towards the goal against the target.

Example codes for grouping goals to use for filtering or presentation.

Codes that reflect the current state of a goal and whether the goal is still being targeted.

Indicates the level of importance associated with reaching or sustaining a goal.

How a compartment must be linked.

Defines how a compartment rule is used.

Possible group measure aggregates (E.g. Mean, Median).

Types of resources that are part of group.

The status of a guidance response.

A code that indicates how the page is generated.

Code of parameter that is input to the guide.

HTTP verbs (in the HTTP command line). See HTTP rfc for details.

Set of handling instructions prior testing of the specimen.

A code that represents the preferred display order of the components of a human name.

This value set includes sample ICD-10 Procedure codes.

Attached is vocabulary for the 27 record lifecycle events, as per ISO TS 21089-2017, Health Informatics - Trusted End-to-End Information Flows, Section 3, Terms and Definitions (2017, at ISO Central Secretariat, passed ballot and ready for publication). This will also be included in the FHIR EHR Record Lifecycle Event Implementation Guide, balloted and (to be) published with FHIR STU-3.

Identifies the purpose for this identifier, if known .

The level of confidence that this link represents the same actual person, based on NIST Authentication Levels.

The status of the ImagingStudy.

This code system supports describing the reason why an administered dose has been assigned a particular status. Often, this reason describes why a dose is considered invalid.

This code system supports describing the validity of a dose relative to a particular recommended schedule.

This code system supports describing the source of the vaccine actually administered. This may be different than the patient eligbility (e.g. the patient may be eligibile for a publically purchased vaccine but due to inventory issues, vaccine purchased with private funds was actually administered).

This code system supports describing the source of the data when the report of the immunization event is not based on information from the person, entity or organization who administered the vaccine.

This code system supports describing the source of the patient’s eligibility for a vaccination program.

This code system supports describing the reason why a dose is considered to be subpotent.

The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the status of the patient relative to a recommended dose. This value set is provided as a suggestive example.

This value set captures the set of indicator codes defined by the CDS Hooks specification.

A classification of the ingredient identifying its precise purpose(s) in the drug product (beyond e.g. active/inactive).

The way in which this manufacturer is associated with the ingredient. For example whether it is a possible one (others allowed), or an exclusive authorized one for this ingredient. Note that this is not the manufacturing process role

A classification of the ingredient identifying its purpose within the product, e.g. active, inactive.

This example value set defines a set of codes that can be used to indicate a type of product plan.

A categorisation for a frequency of occurence of an undesirable effect.

A categorisation for an interaction between two substances.

Codes indicating the kind of the price component.

Codes identifying the lifecycle stage of an Invoice.

How the issue affects the success of the action.

A code that describes the type of issue.

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

This code system defines a defines the set of codes for describing the type or mode of the patient’s preferred language.

The prescription supply types appropriate to a medicinal product

The type of knowledge asset this library contains.

The type of link between this patient resource and another patient resource.

Used to distinguish different roles a resource can play within a set of linked resources.

General reasons for a list to be empty. Reasons are either related to a summary list (i.e. problem or medication list) or to a workflow related list (i.e. consultation list).

Base values for the order of the items in a list resource.

The processing mode that applies to this list.

The current state of the list.

Indicates whether a resource instance represents a specific location or a class of locations.

Indicates whether the location is still in use.

This example code system defines a set of reasons for the cancellation of an appointment.

This example value set defines a set of codes that can be used to indicate the physical form of the Location.

Dose form for a medication, as manufactured (and before any mixing etc.), not necessarily ready for administration to the patient.

The intended usage for supplemental data elements in the measure.

Example Measure Groups for the Measure Resource.

Observation values that indicate what change in a measurement value or score is indicative of an improvement in the measured item or scored issue.

The type of population.

The status of the measure report.

Example Region Value Measure Groups for the Measure Resource.

The type of the measure report.

The scoring type of the measure.

Identifier subgroups in a population for measuring purposes.

Identifier supplemental data in a population for measuring purposes.

The type of measure (includes codes from 2.16.840.1.113883.1.11.20368).

Detailed information about the type of the image - its kind, purpose, or the kind of equipment used to generate it.

Applicable domain for this product (e.g. human, veterinary).

Types of medicinal product packs

Overall defining type of this Medicinal Product.

One of the message events defined as part of this version of FHIR.

The impact of the content of a message.

The protocol used for message transport.

This value set includes sample Missing Tooth Reason codes.

This value set includes sample Modifier type codes.

This value set is suitable for use with the provenance resource. It is derived from, but not compatible with, the HL7 v3 Purpose of use Code system.

The use of a human name.

Identifies the style of unique identifier used to identify a namespace.

Identifies the purpose of the naming system.

The status of a resource narrative.

This value set includes a smattering of Network type codes.

The presentation types of notes.

Codes identifying the lifecycle stage of a product.

Observation Category codes.

This value set defines a set of codes that can be used to indicate the meaning/use of a reference range.

Permitted data type for observation value.

Codes identifying the category of observation range.

Codes providing the status of an observation.

Whether an operation is a normal operation or a query.

Whether an operation parameter is an input or an output parameter.

This value set includes a smattering of FDI oral site codes.

This example value set defines a set of codes that can be used to indicate the role of one Organization in relation to its affiliation with another.

This example value set defines a set of codes that can be used to indicate a type of organization.

A characteristic of a package.

A material used in the construction of packages and their components.

A high level categorisation of a package.

A type of packaging.

Is the Participant required to attend the appointment.

This codesystem defines a set of codes that can be used to indicate how an individual participates in an encounter.

The Participation status of an appointment.

Example Item Flags for the List Resource. In this case, these are the kind of flags that would be used on a medication list at the end of a consultation.

This value set includes smattering of Payment Adjustment Reason codes.

This value set includes a sample set of Payment Status codes.

This value set includes a smattering of Payment Type codes.

This value set includes sample Payment Type codes.

Suitability for age groups, in particular children.

The type of PlanDefinition.

FHIR Specific Example codes for Consent Policy

This value set includes the financial processing priority codes.

Example value set for Procedure Device Action code (what happened to a device during a procedure.

This value set is provided as an exemplar. The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support the procedure performance process.

Confidentiality rating, e.g. commercial sensitivity for a Medicinal Product.

Contact type for a Medicinal Product.

Relationship to another Medicinal Product.

Type of part of a name for a Medicinal Product.

Type of a name for a Medicinal Product.

This value set defines an example set of codes for health program names that could exist for various jurisdictions.

How a property is represented when serialized.

The type of a property value.

How an entity was used in an activity.

The role that a provenance participant played

The type of participation that a provenance agent (participant) played

The lifecycle status of an artifact.

The type of publication such as book, database, or journal.

A rating system that describes the quality of evidence such as the GRADE, DynaMed, or Oxford CEBM systems.

How the Quantity should be understood and represented.

Starter set of user interface control/display mechanisms that might be used when rendering an item in a questionnaire.

Codes defining the purpose of a Questionnaire item of type ‘text’.

The criteria by which a question is enabled.

Distinguishes groups from questions and display text and indicates data type for questions.

Lifecycle status of the questionnaire response.

This value set is provided as an example. The value set to instantiate this attribute should be drawn from a robust terminology code system that consists of or contains concepts to support the medication process.

This value set is provided as an example. The value set to instantiate this attribute should be drawn from a robust terminology code system that consists of or contains concepts to support the medication process.

A set of flags that defines how references are supported.

Whether a reference needs to be version specific or version independent, or whether either can be used.

The methods of referral can be used when referring to a specific HealthCareService resource.

Criterion for rejection of the specimen by laboratory.

The type of relationship to the related artifact.

The outcome of the processing.

The type of relationship between reports.

Evidence Report Section Type.

Codes indicating the degree of authority/intentionality associated with a request.

Identifies the level of importance to be assigned to actioning the request.

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

Codes identifying the lifecycle stage of a request.

The possible types of research elements (E.g. Population, Exposure, Outcome).

Codes for the kind of study objective.

Codes for the stage in the progression of a therapy from initial experimental use in humans in clinical trials to post-market evaluation.

Codes for the main intent of the study.

Codes for why the study ended prematurely.

Codes that convey the current status of the research study.

Indicates the progression of a study subject through a study.

Codes indicating how resources behave from a security perspective

One of the resource types defined as part of this version of FHIR.

How the system supports versioning for a resource.

The kind of response to a message.

The mode of a RESTful capability statement.

Types of security services used with FHIR.

Codes representing the likelihood of a particular outcome in a risk assessment.

SNOMED CT is the most comprehensive and precise clinical health terminology product in the world, owned and distributed around the world by The International Health Terminology Standards Development Organisation (IHTSDO).

The license that applies to an Implementation Guide (using an SPDX license Identifiers, or ‘not-open-source’). The binding is required but new SPDX license Identifiers are allowed to be used (https://spdx.org/licenses/).

What Search Comparator Codes are supported in search.

Why an entry is in the result set - whether it’s included as a match or because of an _include requirement, or to convey information or warning information about the search process.

A supported modifier for a search parameter.

Data types allowed to be used for search parameters.

This CodeSystem contains Additional FHIR-defined Security Role types not defined elsewhere

This value set defines an example set of codes that can be used to classify groupings of service-types/specialties.

The code(s) that detail the conditions under which the healthcare service is available/offered.

This value set defines an example set of codes that can be used to classify groupings of service-types/specialties.

The Digital Signature Purposes, an indication of the reason an entity signs a document. This is included in the signed information and can be used when determining accountability for various actions concerning the document. Examples include: author, transcriptionist/recorder, and witness.

How slices are interpreted when evaluating an instance.

The free/busy status of the slot.

Codes that define what the server is capable of.

The possible sort directions, ascending or descending.

This codesystem defines a set of codes that can be used to indicate the kinds of special arrangements in place for a patient’s visit.

Extra measures defined for a Medicinal Product, such as requirement to conduct post-authorisation studies.

A set of generally useful codes defined so they can be included in value sets.

Degree of preference of a type of conditioned specimen.

Codes providing the status/availability of a specimen.

Status codes indicating the ‘standards’ level of an artifact

The role that the assertion variable plays.

The role that the assertion variable plays.

A rating system that describes the strength of the recommendation, such as the GRADE, DynaMed, or HGPS systems.

Structure Definition Use Codes / Keywords

Defines the type of structure that a definition is describing.

How to interpret the context.

If this is the default rule set to apply for the source type, or this combination of types.

Mode for this instance of data.

How the referenced structure is used in this mapping.

If field is a list, how to manage the source.

If field is a list, how to manage the production.

How data is copied/created.

The type of study the evidence was derived from.

This value set includes codes for the relationship between the Subscriber and the Beneficiary (insured/covered party/patient).

The type of method used to execute a subscription.

The type of notification represented by the status message.

This codesystem defines a set of codes that can be used to filter Subscription triggers.

The status of a subscription.

The type of a numeric quantity measurement.

The optical rotation type of a substance.

The relationship between two substance types.

The stereochemistry type of a substance.

This value sets refers to a specific supply item.

This value sets refers to a Category of supply.

Status of the supply delivery.

The reason why the supply item was requested.

Status of the supply request.

This value set includes a smattering of FDI tooth surface codes.

Types of combining results from a body of evidence (eg. summary data meta-analysis).

A species for which a medicinal product is intended.

Codes indicating the type of action that is expected to be performed

Distinguishes whether the task is a proposal, plan or full order.

The current status of the task.

Life cycle of the Status Code of a Template Design (Version)

The results of executing an action.

The type of participant.

The reported execution result.

The current status of the test report.

This value set defines a set of codes that are used to indicate the supported operations of a testing engine or tool.

This value set defines a set of codes that are used to indicate the profile type of a test system when acting as the destination within a TestScript.

This value set defines a set of codes that are used to indicate the profile type of a test system when acting as the origin within a TestScript.

The allowable request method or HTTP operation codes.

Classification of relationship between a therapy and a contraindication or an indication.

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

The type of trigger.

How a type relates to its baseDefinition.

Codes to identify how UDI data was entered.

This value set includes a smattering of USCLS codes.

A categorisation for a frequency of occurence of an undesirable effect.

This value set includes a smattering of Unit type codes.

The presentation type in which an administrable medicinal product is given to a patient.

A code that specifies a type of context being specified by a usage context.

The purpose of the Claim: predetermination, preauthorization, claim.

This code system defines the methods by which entities participating in a validation process share information (e.g. submission/retrieval of attested information, or exchange of validated information).

A coded concept listing the base codes.

A coded concept listing the eye codes.

This value set includes W3C PROV Data Model Activity concepts, which are treated as codes in this valueset. Some adaptations were made to make these concepts suitable values for the Provenance.activity element. Coded concepts are from PROV-DM and the display names are their counterparts in PROV-N (human readable notation syntax specification).[code system OID: http://www.w3.org/TR/2013/REC-prov-dm-20130430/ and http://www.w3.org/TR/2013/REC-prov-n-20130430/]

Classification of warning type.

How a search parameter relates to the set of elements returned by evaluating its xpath query.

Ability of the primary source to push updates/alerts

Chromosome number for human.

The result if validation fails

HL7-defined table of codes which identify conditions under which acknowledgments are required to be returned in response to a message.

The frequency with which the target must be validated

Type for orientation.

Type of the validation primary source

Type of alerts/updates the primary source can send

Type for quality report.

Type for access of external URI.

Type if a sequence – DNA, RNA, or amino acid sequence.

The validation status of the target

Type for strand.

The primary process by which the target is validated

Status of the validation of the target against the primary source

What the target is validated against