Confirmation

Testing stuff

The US Core AllergyIntolerance Profile inherits from the FHIR [AllergyIntolerance](https hl7.org fhir R4 allergyintolerance.html) resource; refer to it for scope and usage definitions. This profile sets minimum expectations for the AllergyIntolerance resource to record search and fetch allergies adverse reactions associated with a patient. It specifies which core elements extensions vocabularies and value sets **SHALL** be present and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption.

The US Core Body Weight Profile inherits from the US Core Vital Signs Profile. This profile sets minimum expectations for the Observation resource to record search and fetch body weight observations with a standard LOINC code and UCUM units of measure. It specifies which *additional* core elements extensions vocabularies and value sets **SHALL** be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption.

The US Core Condition Encounter Diagnosis Profile inherits from the FHIR [Condition](https hl7.org fhir R4 condition.html) resource; refer to it for scope and usage definitions. US Core version 5.0.0 split the US Core Condition Profile into this profile and the US Core Condition Problems and Health Concerns Profile. This profile meets the requirements of the U.S. Core Data for Interoperability (USCDI) *Encounter Diagnosis* Data Element. It sets minimum expectations for the Condition resource to record search and fetch information about an encounter diagnosis. It specifies which core elements extensions vocabularies and value sets **SHALL** be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption.

The US Core Condition Problems and Health Concerns Profile inherits from the FHIR [Condition](https hl7.org fhir R4 condition.html) resource; refer to it for scope and usage definitions. US Core version 5.0.0 split the US Core Condition Profile into this profile and the US Core Condition Encounter Diagnosis Profile. This profile meets the requirements of the U.S. Core Data for Interoperability (USCDI) *Problems* *Health Concerns* and *SDOH Problems Health Concerns* Data Elements. It sets minimum expectations for the Condition resource to record search and fetch information about a condition diagnosis or another event situation issue or clinical concept documented and categorized as a problem or health concern including information about a Social Determinants of Health related condition. It specifies which core elements extensions vocabularies and value sets **SHALL** be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption.

The US Core Device Profile inherits from the FHIR [Device](https hl7.org fhir R4 device.html) resource; refer to it for scope and usage definitions. This profile meets the requirements of the U.S. Core Data for Interoperability (USCDI) *Unique Device Identifier - Implantable* Data Element. It sets minimum expectations for the Device resource to record search and fetch UDI information associated with a patient's implantable device(s). It specifies which core elements extensions vocabularies and value sets **SHALL** be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption.

Location of type Hospital

The US Core Advance Directive Information (ADI) DocumentReference Profile inherits from the FHIR [DocumentReference](https hl7.org fhir R4 documentreference.html) resource; refer to it for scope and usage definitions. This profile and the [US Core Observation ADI Documentation Profile](StructureDefinition-us-core-observation-adi-documentation.html) meet the [U.S. Core Data for Interoperability (USCDI)](https www.healthit.gov isp united-states-core-data-interoperability-uscdi) *Advance Directive Observation* Data Element requirements. It sets minimum expectations for searching and fetching patient Advance Directive Information (ADI) documents using the DocumentReference resource. Examples of advance healthcare directive documents include physician order for life sustaining treatment (POLST) do not resuscitate order (DNR) and medical power of attorney. In addition to the document contents it communicates the type of advance directive document the author the verifier and other properties. To represent whether advance directive documents exist for a patient see the US Core Observation ADI Documentation Profile. This profile sets minimum expectations for searching and fetching patient ADI documents using the DocumentReference resource. It specifies which core elements extensions vocabularies and value sets **SHALL** be present and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption.

The US Core BMI Profile inherits from the US Core Vital Signs Profile. This profile sets minimum expectations for the Observation resource to record search and fetch Body Mass Index (BMI) observations with a standard LOINC codes and UCUM units of measure. It specifies which *additional* core elements extensions vocabularies and value sets **SHALL** be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption.

The US Core Body Temperature Profile inherits from the US Core Vital Signs Profile. This profile sets minimum expectations for the Observation resource to record search and fetch body temperature observations with a standard LOINC code and UCUM units of measure. It specifies which *additional* core elements extensions vocabularies and value sets **SHALL** be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption.