HL7 FHIR Implementation Guide: Objective FHIR, Release 0.8

Publish Box goes here

Primary local value sets used in this Implementation Guide

Name Definition
AbnormalBodyStructureVS

A morphologically altered or physiology.

AttributionCategoryVS

Whether the adverse event is attributed to a treatment, course of the disease, medical error, unrelated to either, or unknown.

BodyLocationVS

Codes that describe normal and pathologic anatomic systems, regions, cavities, and spaces. The code set includes codes from the SNOMED CT hierarchy descending from 123037004 ‘Body Structure’.

Body location is a flexible structure that allows the location to be determined by a single code, or a code plus laterality and/or orientation. The body location can also be specified in relation to one or more body landmarks. SNOMED CT is used in all cases.

  • Code only: The code should include (precoordinate) laterality and/orientation to the degree necessary to completely specify the body location.
  • Code plus laterality and/or orientation: The basic code augmented by codes specifying the body side and/or anatomical orientation.
  • Relation to landmark: The location relative to a landmark is specified by:
  • Establishing the location and type of landmark using a body site code and optional laterality/orientation, and
  • Specifying the direction and distance from the landmark to the body location.

Note that BodyLocation is a data type (a reusable structure), not a stand-alone entity. The concept is similar to how a postal address can apply to a person, location, or organization. This contrasts with FHIR’s stand-alone BodySite (aka BodyStructure in r4) which ‘is not … intended for describing the type of anatomical location but rather a specific body site on a specific patient’ (FHIR 3.5).

ComorbidConditionVS

SNOMED and ICD-10 codes for common comorbid conditions. Aligns with Elixhauser comorbidity scale. ICD-10 codes are drawn from https://www.hcup-us.ahrq.gov/toolssoftware/comorbidityicd10/comformat_icd10cm_2019_1.txt

ConditionCategoryVS

A category assigned to the condition, for example, a disease, concern, symptom, functional impairment, or structural abnormality. Extends http://hl7.org/fhir/ValueSet/condition-category by including all codes from the corresponding code system, namely, http://terminology.hl7.org/CodeSystem/condition-category. Extensions are based on http://fhir.org/guides/argonaut/ValueSet/condition-category, but substituting SNOMED CT codes.

CongenitalAbnormalitiesVS
DiagnosticImagingVS

Codes describing imaging procedures. Value set includes SNOMED codes descending from 363679005 ‘Imaging (procedure)’.

ECOGPerformanceStatusVS

Value set for Eastern Cooperative Oncology Group performance status. Values range from grade 0 (Asymptomatic) to grade 5 (Dead).

GradedFrequencyVS

Answers to ‘how often’ questions. A 5-value qualitative scale of frequency of an event equivalent to LL1016-6, LL1024-0, LL346-8.

KarnofskyPerformanceStatusVS

Value set for Karnofsky Performance Status, with codes for each decade from 100 to 0. Higher scores are associated with better functional status, with 100 representing no symptoms or evidence of disease, and 0 representing death. This value set corresponds to LOINC list LL4986-7

LateralityVS

Terms that specify the side of the body. The laterality value set is part of BodyLocation, a flexible structure that allows the location to be determined by a single code, or a code plus laterality and/or orientation. The body location can also be specified in relation to one or more body landmarks. SNOMED CT is used in all cases.

  • Code only: The code should include (precoordinate) laterality and/orientation to the degree necessary to completely specify the body location.
  • Code plus laterality and/or orientation: The basic code augmented by codes specifying the body side and/or anatomical orientation.
  • Relation to landmark: The location relative to a landmark is specified by:
  • Establishing the location and type of landmark using a body site code and optional laterality/orientation, and
  • Specifying the direction and distance from the landmark to the body location.

Note that BodyLocation is a data type (a reusable structure), not a stand-alone entity. The concept is similar to how a postal address can apply to a person, location, or organization. This contrasts with FHIR’s stand-alone BodySite (aka BodyStructure in r4) which ‘is not … intended for describing the type of anatomical location but rather a specific body site on a specific patient’ (FHIR 3.5).

MedDRAVS
MedicationNonAdherenceReasonVS
OrientationVS

Terms that specify anatomical orientation. The orientation value set is part of BodyLocation, a flexible structure that allows the location to be determined by a single code, or a code plus laterality and/or orientation. The body location can also be specified in relation to one or more body landmarks. SNOMED CT is used in all cases.

  • Code only: The code should include (precoordinate) laterality and/orientation to the degree necessary to completely specify the body location.
  • Code plus laterality and/or orientation: The basic code augmented by codes specifying the body side and/or anatomical orientation.
  • Relation to landmark: The location relative to a landmark is specified by:
  • Establishing the location and type of landmark using a body site code and optional laterality/orientation, and
  • Specifying the direction and distance from the landmark to the body location.

Note that BodyLocation is a data type (a reusable structure), not a stand-alone entity. The concept is similar to how a postal address can apply to a person, location, or organization. This contrasts with FHIR’s stand-alone BodySite (aka BodyStructure in r4) which ‘is not … intended for describing the type of anatomical location but rather a specific body site on a specific patient’ (FHIR 3.5).

QuantitativeResultInterpretationVS

Interpretations of abnormal quantitative results.

RadiationProcedureVS

Codes describing radiation therapy procedures. The value set includes a limited set of radiation modality codes from SNOMED CT, however, ICD-10-PCS code from Section D (Radiation Therapy) and appropriate CPT radiation procedure codes are also considered compliant. CPT codes are not explicitly included due to licensing restrictions. ICD-10-PCS codes are not included because they are not currently supported by the FHIR IG Publishing tool.

RadiationTargetBodySiteVS

Codes for body sites that can be targets of radiation therapy. This list of sites is based on Commission on Cancer’s ‘Standards for Oncology Registry Entry  - STORE 2018’. This value set contains SNOMED CT equivalent terms.

ResearchSubjectTerminationReasonVS

The reason for a research subject leaving a research study.

SettingVS

What type of place is found at a given location. More than one descriptor may be applicable.

StudyArmTypeVS

The role of each arm in the clinical trial.

FHIR is currently unable to handle values from NCI Thesaurus, so no values are listed in the Expansion, below. The values ARE in the downloads. For convenience, here is a listing of values in this value set: NCIT#C94487 ‘Intervention Group’ NCIT#C68609 ‘Active Comparator’ NCIT#C49648 ‘Placebo Control’ NCIT#C116527 ‘Sham Intervention’

SurgicalBodyLocationRoleVS

Roles of body site in surgical procedures. Value set includes codes from the SNOMED hierarchy descending from 363704007 ‘Procedure site’ and descending from 272737002 ‘Site of (attribute)’.

SurgicalMethodVS

Codes describing additional information about the method of the surgery. Includes the technique used to reach the site of the procedure, and actions taken during the surgery. Value set includes SNOMED codes descending from 103379005 ‘Procedural approach’ and descending from 129284003 ‘Surgical action’.

SurgicalProcedureVS

Codes describing surgical procedures. Includes codes from SNOMED CT under the hierarchy of 387713003 ‘Surgical procedure’. Codes from ICD-10-PCS and CPT are acceptable. CPT codes are not listed here due to intellectual property restrictions. ICD-10-PCS codes are not listed because of a limitation in the FHIR Implementation Guide publisher. For CPT and ICD-10-PCS, only codes representing surgical procedures should be included.

TreatmentIntentVS

The purpose of a treatment. The value set includes ‘curative’ and ‘palliative’. Curative is defined as any treatment meant to reduce or control a disease process, even if a ‘cure’ is not anticipated. Palliative includes treatments meant to reduce symptoms and side effects, such as antiemetics.

TreatmentTerminationReasonVS

Values used to describe the reasons for stopping a treatment. Includes code for ‘treatment completed’ as well as codes for unplanned (early) stoppage. Applies to medications and other treatments that take place over a period of time, such as radiation treatments.

Primary external value sets used in this Implementation Guide

Name Definition
AdministrativeGender

The gender of a person used for administrative purposes.

AdministrativeGender

The gender of a person used for administrative purposes.

AdmitSource

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

AdverseEventActuality

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

AdverseEventCategory

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

AdverseEventCausalityAssessment

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

AdverseEventCausalityMethod

TODO.

AdverseEventOutcome

TODO (and should this be required?).

AdverseEventSeriousness

Overall seriousness of this event for the patient.

AdverseEventSeverity

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

AdverseEventSeverity

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

All Security Labels

A single value set for all security labels defined by FHIR.

AllergyIntoleranceCategory

Category of an identified substance associated with allergies or intolerances.

AllergyIntoleranceClinicalStatusCodes

Preferred value set for AllergyIntolerance Clinical Status.

AllergyIntoleranceCriticality

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

AllergyIntoleranceSeverity

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

AllergyIntoleranceSubstance/Product,ConditionAndNegationCodes

This value set includes concept codes for specific substances/pharmaceutical products, allergy or intolerance conditions, and negation/exclusion codes to specify the absence of specific types of allergies or intolerances.

AllergyIntoleranceType

Identification of the underlying physiological mechanism for a Reaction Risk.

AllergyIntoleranceVerificationStatusCodes

Preferred value set for AllergyIntolerance Verification Status.

AppointmentCancellationReason

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

AppointmentStatus

The free/busy status of an appointment.

CommonLanguages

This value set includes common codes from BCP-47 (http://tools.ietf.org/html/bcp47)

CompositionAttestationMode

The way in which a person authenticated a composition.

CompositionStatus

The workflow/clinical status of the composition.

Condition/DiagnosisSeverity

Preferred value set for Condition/Diagnosis severity grading.

Condition/Problem/DiagnosisCodes

Example value set for Condition/Problem/Diagnosis codes.

ConditionCategoryCodes

Preferred value set for Condition Categories.

ConditionClinicalStatusCodes

Preferred value set for Condition Clinical Status.

ConditionStage

Example value set for stages of cancer and other conditions.

ConditionStageType

Example value set for the type of stages of cancer and other conditions

ConditionVerificationStatus

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

ContactEntityType

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.

Context of Use ValueSet

This value set defines a base set of codes that can be used to indicate that the content in a resource was developed with a focus and intent of supporting use within particular contexts.

CoverageClassCodes

This value set includes Coverage Class codes.

CoverageCopayTypeCodes

This value set includes sample Coverage Copayment Type codes.

CoverageTypeAndSelf-PayCodes

This value set includes Coverage Type codes.

DataAbsentReason

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

DaysOfWeek

The days of the week.

DesignationUse

Details of how a designation would be used

DeviceNameType

The type of name the device is referred by.

DiagnosisRole

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.

DiagnosticReportStatus

The status of the diagnostic report.

DiagnosticServiceSectionCodes

This value set includes all the codes in HL7 V2 table 0074.

Diet

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

DischargeDisposition

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

DocumentClassValueSet

This is the code specifying the high-level kind of document (e.g. Prescription, Discharge Summary, Report, etc.). Note: Class code for documents comes from LOINC, and is based upon one of the following:The type of service described by the document. It is described at a very high level in Section 7.3 of the LOINC Manual. The type study performed. It was determined by identifying modalities for study reports. The section of the chart where the document is placed. It was determined from the SETs created for Claims Attachment requests.

DocumentReferenceFormatCodeSet

The value set is defined to be the set of format codes defined by the IHE Technical Framework, and also including additional format codes defined by the HL7. The value set is listed in HITSP C80 Table 2-153 Format Code Value Set Definition, with additions published later by IHE as published at http://wiki.ihe.net/index.php?title=IHE_Format_Codes and with additions published later by HL7 as published at https://confluence.hl7.org/display/SD/Format+Codes+for+IHE+XDS. This is the code specifying the technical format of the document. Along with the typeCode, it should provide sufficient information to allow any potential document consumer to know if it will be able to process the document. The code shall be sufficiently specific to ensure processing/display by identifying a document encoding, structure and template. The actual list of codes here is incomplete

DocumentReferenceStatus

The status of the document reference.

DocumentRelationshipType

The type of relationship between documents.

DocumentSectionCodes

Document section codes (LOINC codes used in CCDA sections).

DocumentTypeValueSet

This is the code specifying the precise type of document (e.g. Pulmonary History and Physical, Discharge Summary, Ultrasound Report, etc.). The Document Type value set includes all LOINC values listed in HITSP C80 Table 2-144 Document Class Value Set Definition above used for Document Class, and all LOINC values whose SCALE is DOC in the LOINC database.

EnableWhenBehavior

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

EncounterLocationStatus

The status of the location.

EncounterReasonCodes

This examples value set defines the set of codes that can be used to indicate reasons for an encounter.

EncounterStatus

Current state of the encounter.

EpisodeOfCareStatus

The status of the episode of care.

EpisodeOfCareType

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

EventStatus

Codes identifying the lifecycle stage of an event.

ExampleCoverageFinancialExceptionCodes

This value set includes Example Coverage Financial Exception Codes.

ExampleUseCodesForList

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

FHIRDeviceStatus

The availability status of the device.

FHIRDeviceStatusReason

The availability status reason of the device.

FHIRDeviceTypes

Codes used to identify medical devices. Includes concepts from SNOMED CT (http://www.snomed.org/) where concept is-a 49062001 (Device) and is provided as a suggestive example.

FHIRDocumentTypeCodes

FHIR Document Codes - all LOINC codes where scale type = ‘DOC’.

FHIRSpecimenCollectionMethod

This example value set defines a set of codes that can be used to indicate the method by which a specimen was collected.

FHIRSubstanceStatus

A code to indicate if the substance is actively used.

FacilityTypeCodeValueSet

This is the code representing the type of organizational setting where the clinical encounter, service, interaction, or treatment occurred. The value set used for Healthcare Facility Type has been defined by HITSP to be the value set reproduced from HITSP C80 Table 2-147.

FilterOperator

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

FinancialResourceStatusCodes

This value set includes Status codes.

GroupType

Types of resources that are part of group.

Jurisdiction ValueSet

This value set defines a base set of codes for country, country subdivision and region for indicating where a resource is intended to be used.

Note: The codes for countries and country subdivisions are taken from ISO 3166 while the codes for “supra-national” regions are from UN Standard country or area codes for statistical use (M49).

LOINCCodes

This value set includes all LOINC codes

LOINCDiagnosticReportCodes

This value set includes LOINC codes that relate to Diagnostic Observations.

LinkType

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

ListEmptyReasons

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).

ListMode

The processing mode that applies to this list.

ListOrderCodes

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

ListStatus

The current state of the list.

LocationMode

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

LocationStatus

Indicates whether the location is still in use.

LocationType

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

Marital Status Codes

This value set defines the set of codes that can be used to indicate the marital status of a person.

MediaCollectionView/Projection

Codes defined in SNOMED CT that can be used to record Media Recording views.

MediaModality

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

Medication Status Codes

Medication Status Codes

Medication Status Codes

Medication Status Codes

Medication Status Codes

Medication Status Codes

MedicationAdministration Category Codes

MedicationAdministration Category Codes

MedicationAdministration Status Codes

MedicationAdministration Status Codes

ObservationCategoryCodes

Observation Category codes.

ObservationInterpretationCodes

A categorical assessment, providing a rough qualitative interpretation of the observation value, such as “normal”/ “abnormal”,”low” / “high”, “better” / “worse”, “susceptible” / “resistant”, “expected”/ “not expected”. The value set is intended to be for ANY use where coded representation of an interpretation is needed.

Notes:

This is being communicated in v2.x in OBX-8 (Observation Interpretation), in v3 in ObservationInterpretation (CWE) in R1 (Representative Realm) and in FHIR in Observation.interpretation. Historically these values come from the laboratory domain, and these codes are extensively used. The value set binding is extensible, so codes outside the value set that are needed for interpretation concepts (i.e. particular meanings) that are not included in the value set can be used, and these new codes may also be added to the value set and published in a future version.

ObservationMethods

Observation Method codes from SNOMED CT where concept is-a 272394005 (Technique (qualifier value)) or is-a 129264002 (Action (qualifier value)) or is-a 386053000 (Evaluation procedure(procedure))

ObservationReferenceRangeAppliesToCodes

This value set defines a set of codes that can be used to indicate the particular target population the reference range applies to.

ObservationReferenceRangeMeaningCodes

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

ObservationStatus

Codes providing the status of an observation.

OrganizationType

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

ParticipantRequired

Is the Participant required to attend the appointment.

ParticipantRoles

Roles of participants that may be included in a care team. Defined as: Is a Person, Healthcare professional (occupation) or Healthcare related organization (qualifier value).

ParticipantType

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

ParticipationStatus

The Participation status of an appointment.

PatientContactRelationship

The nature of the relationship between the patient and the contact person.

PatientMedicineChangeTypes

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.

PatientRelationshipType

A set of codes that can be used to indicate the relationship between a Patient and a Related Person.

PracticeSettingCodeValueSet

This is the code representing the clinical specialty of the clinician or provider who interacted with, treated, or provided a service to/for the patient. The value set used for clinical specialty has been limited by HITSP to the value set reproduced from HITSP C80 Table 2-149 Clinical Specialty Value Set Definition.

ProcedureCategoryCodes(SNOMEDCT)

Procedure Category code: A selection of relevant SNOMED CT codes.

ProcedureCodes(SNOMEDCT)

Procedure Code: All SNOMED CT procedure codes.

ProcedureDeviceActionCodes

Example codes indicating the change that happened to the device during the procedure. Note that these are in no way complete and might not even be appropriate for some uses.

ProcedureFollowUpCodes(SNOMEDCT)

Procedure follow up codes: A selection of SNOMED CT codes relevant to procedure follow up.

ProcedureNotPerformedReason(SNOMED-CT)

Situation codes describing the reason that a procedure, which might otherwise be expected, was not performed, or a procedure that was started and was not completed. Consists of SNOMED CT codes, children of procedure contraindicated (183932001), procedure discontinued (416406003), procedure not done (416237000), procedure not indicated (428119001), procedure not offered (416064006), procedure not wanted (416432009), procedure refused (183944003), and procedure stopped (394908001).

ProcedureOutcomeCodes(SNOMEDCT)

Procedure Outcome code: A selection of relevant SNOMED CT codes.

ProcedurePerformerRoleCodes

This example value set defines the set of codes that can be used to indicate a role of a procedure performer.

ProcedureReasonCodes

This example value set defines the set of codes that can be used to indicate a reason for a procedure.

ProvenanceActivityType

This value set contains representative Activity Type codes, which includes codes from the HL7 DocumentCompletion, ActStatus, and DataOperations code system, W3C PROV-DM and PROV-N concepts and display names, several HL7 Lifecycle Event codes for which there are agreed upon definitions, and non-duplicated codes from the HL7 Security and Privacy Ontology Operations codes.

ProvenanceEntityRole

How an entity was used in an activity.

ProvenanceParticipantType

The type of participation a provenance participant.

PublicationStatus

The lifecycle status of an artifact.

QuantityComparator

How the Quantity should be understood and represented.

QuestionnaireAnswerCodes

Example list of codes for answers to questions. (Not complete or necessarily appropriate.)

QuestionnaireItemOperator

The criteria by which a question is enabled.

QuestionnaireItemType

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

QuestionnaireQuestionCodes

Example list of codes for questions and groups of questions. (Not necessarily complete or appropriate.)

QuestionnaireResponseStatus

Lifecycle status of the questionnaire response.

ReasonMedicationGivenCodes

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.

RequestIntent

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

RequestPriority

The clinical priority of a diagnostic order.

RequestStatus

Codes identifying the lifecycle stage of a request.

ResearchStudyObjectiveType

Codes for the kind of study objective.

ResearchStudyPhase

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

ResearchStudyPrimaryPurposeType

Codes for the main intent of the study.

ResearchStudyReasonStopped

Codes for why the study ended prematurely.

ResearchStudyStatus

Codes that convey the current status of the research study.

ResearchSubjectStatus

Indicates the progression of a study subject through a study.

ResourceType

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

ResourceType

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

SNOMEDCTAdministrationMethodCodes

This value set includes some method codes from SNOMED CT - provided as an exemplar

SNOMEDCTClinicalFindings

This value set includes all the “Clinical finding” SNOMED CT codes - concepts where concept is-a 404684003 (Clinical finding (finding)).

SNOMEDCTDrugTherapyStatusCodes

This value set includes some taken and not taken reason codes from SNOMED CT - provided as an exemplar

SNOMEDCTFormCodes

This value set includes all dose form codes from SNOMED CT - provided as an exemplar.

SNOMEDCTMedicationAsNeededReasonCodes

This value set includes all clinical findings from SNOMED CT - provided as an exemplar value set.

SNOMEDCTMedicationCodes

This value set includes all drug or medicament substance codes and all pharmaceutical/biologic products from SNOMED CT - provided as an exemplar value set.

SNOMEDCTReasonMedicationNotGivenCodes

This value set includes all medication refused, medication not administered, and non-administration of necessary drug or medicine codes from SNOMED CT - provided as an exemplar value set.

SNOMEDCTRouteCodes

This value set includes all Route codes from SNOMED CT - provided as an exemplar.

SecurityRoleType

This example FHIR value set is comprised of example Actor Type codes, which can be used to value FHIR agents, actors, and other role elements such as those specified in financial transactions. The FHIR Actor value set is based on DICOM Audit Message, C402; ASTM Standard, E1762-95 [2013]; selected codes and derived actor roles from HL7 RoleClass OID 2.16.840.1.113883.5.110; HL7 Role Code 2.16.840.1.113883.5.111, including AgentRoleType; HL7 ParticipationType OID: 2.16.840.1.113883.5.90; and HL7 ParticipationFunction codes OID: 2.16.840.1.113883.5.88. This value set includes, by reference, role codes from external code systems: NUCC Health Care Provider Taxonomy OID: 2.16.840.1.113883.6.101; North American Industry Classification System [NAICS]OID: 2.16.840.1.113883.6.85; IndustryClassificationSystem 2.16.840.1.113883.1.11.16039; and US Census Occupation Code OID: 2.16.840.1.113883.6.243 for relevant recipient or custodian codes not included in this value set. If no source is indicated in the definition comments, then these are example FHIR codes. It can be extended with appropriate roles described by SNOMED as well as those described in the HL7 Role Based Access Control Catalog and the HL7 Healthcare (Security and Privacy) Access Control Catalog. In Role-Based Access Control (RBAC), permissions are operations on an object that a user wishes to access. Permissions are grouped into roles. A role characterizes the functions a user is allowed to perform. Roles are assigned to users. If the user’s role has the appropriate permissions to access an object, then that user is granted access to the object. FHIR readily enables RBAC, as FHIR Resources are object types and the CRUDE events (the FHIR equivalent to permissions in the RBAC scheme) are operations on those objects. In Attribute-Based Access Control (ABAC), a user requests to perform operations on objects. That user’s access request is granted or denied based on a set of access control policies that are specified in terms of attributes and conditions. FHIR readily enables ABAC, as instances of a Resource in FHIR (again, Resources are object types) can have attributes associated with them. These attributes include security tags, environment conditions, and a host of user and object characteristics, which are the same attributes as those used in ABAC. Attributes help define the access control policies that determine the operations a user may perform on a Resource (in FHIR) or object (in ABAC). For example, a tag (or attribute) may specify that the identified Resource (object) is not to be further disclosed without explicit consent from the patient.

ServiceCategory

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

ServiceRequestCategoryCodes

An example value set of SNOMED CT concepts that can classify a requested service

ServiceType

This value set defines an example set of codes of service-types.

SpecialArrangements

This value set defines a set of codes that can be used to indicate the kinds of special arrangements in place for a patients visit.

SpecialCourtesy

This value set defines a set of codes that can be used to indicate special courtesies provided to the patient.

SpecimenContainerType
Checks on the patient prior specimen collection. All SNOMED CT concepts descendants of 706041008 Device for body fluid and tissue collection/transfer/processing (physical object)
SpecimenProcessingProcedure

The technique that is used to perform the process or preserve the specimen.

SpecimenStatus

Codes providing the status/availability of a specimen.

SubscriberRelationshipCodes

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

SubstanceCategoryCodes

Substance category codes

SubstanceCode

This value set contains concept codes for specific substances. It includes codes from SNOMED where concept is-a 105590001 (Substance (substance)) and where concept is-a 373873005 (Pharmaceutical / biologic product (product))

UDIEntryType

Codes to identify how UDI data was entered.

USCoreMedicationCodes

All prescribable medication formulations represented using either a ‘generic’ or ‘brand-specific’ concept. This includes RxNorm codes whose Term Type is SCD (semantic clinical drug), SBD (semantic brand drug), GPCK (generic pack), BPCK (brand pack), SCDG (semantic clinical drug group), SBDG (semantic brand drug group), SCDF (semantic clinical drug form), or SBDF (semantic brand drug form)

USCoreProblem

This describes the problem. Diagnosis/Problem List is broadly defined as a series of brief statements that catalog a patient’s medical, nursing, dental, social, preventative and psychiatric events and issues that are relevant to that patient’s healthcare (e.g., signs, symptoms, and defined conditions)

USCoreProcedureCodes

This example value set defines a set of codes that can be used to indicate the type of procedure: a specific code indicating type of procedure performed, from CPT or SNOMED CT.

UsageContextType

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

http://fhir.org/guides/argonaut-clinicalnotes/ValueSet/documentreference-category
http://h7.org/fhir/us/core/ValueSet/us-core-medication-codes
http://hl7.org/fhir/ValueSet/c80-doc-classcodes
http://hl7.org/fhir/ValueSet/digital-media-type
http://hl7.org/fhir/ValueSet/v2-0276
http://hl7.org/fhir/ValueSet/v2-0487
http://hl7.org/fhir/ValueSet/v2-2.7-0360
http://hl7.org/fhir/ValueSet/v3-ActCode
http://hl7.org/fhir/ValueSet/v3-ActEncounterCode
http://hl7.org/fhir/ValueSet/v3-ActPriority
http://hl7.org/fhir/ValueSet/v3-ServiceDeliveryLocationRoleType
http://hl7.org/fhir/ValueSet/v3-SubstanceAdminSubstitutionReason
http://hl7.org/fhir/us/core/ValueSet-us-core-substance.html
http://terminology.hl7.org/ValueSet/v2-0092
http://terminology.hl7.org/ValueSet/v2-0116
http://terminology.hl7.org/ValueSet/v2-0371
http://terminology.hl7.org/ValueSet/v2-0493
http://terminology.hl7.org/ValueSet/v2-0916
http://terminology.hl7.org/ValueSet/v3-ActEncounterCode
http://terminology.hl7.org/ValueSet/v3-ActSubstanceAdminSubstitutionCode
http://terminology.hl7.org/ValueSet/v3-ConfidentialityClassification
http://terminology.hl7.org/ValueSet/v3-PurposeOfUse
http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType
medicationRequest Course of Therapy Codes

MedicationRequest Course of Therapy Codes

medicationRequest Intent

MedicationRequest Intent Codes

medicationRequest Status Reason Codes

MedicationRequest Status Reason Codes

medicationrequest Status

MedicationRequest Status Codes