--- tags: USCDI v4 title: Facility Information cat: moderate --- <style>.markdown-body { max-width: 1500px; }</style> Physical place of available services or resources. ## :new: :building_construction: Facility Information Data Elements <!-- quote --> Draft ![](https://hackmd.io/_uploads/BJr4UjTXn.png) Final ![](https://hackmd.io/_uploads/r1X7F66c2.png) <!-- table --> DATA ELEMENT|APPLICABLE VOCABULARY STANDARD(S)<br/>Standards listed are required. If more than one is listed, at least one is required unless otherwise noted. If a cell is empty, an applicable vocabulary standard has not been identified.|US Core V6 Proposal ---|---|--- **Facility Identifier**<br/>Sequence of characters representing a physical place of available services or resources.||:new: : US Core`Location.identifier` 0..* Must Support **Facility Type**<br/>Category of service or resource available in a location.<br/><br/>Examples include but are not limited to hospital, laboratory, pharmacy, ambulatory clinic, longterm and post-acute care facility, and food pantry||:new:: US Core`Location.type` 0..* Must Support, Binding: [ServiceDeliveryLocationRoleType](http://terminology.hl7.org/5.0.0/ValueSet-v3-ServiceDeliveryLocationRoleType.html) (extensible) **Facility Name**<br/>Word or words by which a facility is known.||**No Change**: US Core`Location.name` is a Must Support element ### Known issues ONC Clarification: Encounter.location vs :Question: - [Relationships between Practitioner, Organization, Location, and Endpoints](http://www.fhir.org/guides/argonaut/pd//release1/guidance.html) - [Location Hierarchy](https://hl7.org/fhir/R4/location.html) `Location.type` - a Must Support vs USCDI requirement? - `terminology candidates: 1. C-CDA Value set: [HealthcareServiceLocation](https://vsac.nlm.nih.gov/valueset/2.16.840.1.113883.1.11.20275/expansion/Latest) vs 2. FHIR [ServiceDeliveryLocationRoleType](http://terminology.hl7.org/5.0.0/ValueSet-v3-ServiceDeliveryLocationRoleType.html) (extensible) - Search by type? ### Next Steps List of relevent US Core Profiles that support links to Location and Encounter (typically `.location` and `.encounter` elements) :thinking_face: Should US Core support location everywhere is appropriate as a MS/USCDI ? Took ["facility information" Poll](https://chat.fhir.org/#narrow/stream/179175-argonaut/topic/Early.20US.20Core.207.2E0.2E0.20Designs/near/385614207) final tally option-1 3,option-2 1,option-3 1 Based on discussion on the August 30: - add .encounter as MS to the Profiles listed below - in addition add .location to to the Immunization Profile - add implementer guidance, that if the actual event location != to Encounter.location SHOULD use the .location to clarify. note despite location info being appropraite for speciment collection, Specimen has neither a `.location` or `.encounter` element. and MedicationDispense.context #### US Core (FHIR) |US Core Resource|Location Appropriate Here?|Any current Constraints|Reference(Encounter)|Reference(Location)| |--- |--- |--- |--- |--- | |CarePlan|No|||| |Device|No|||| |DiagnosticReport (Lab)|Yes|No|DiagnosticReport.encounter|Not included - potential extension| |DiagnosticReport (Notes)|Yes|**Yes**|**DiagnosticReport.encounter (MS)**|Not included - potential extension| |Encounter|Yes|**Yes**|Encounter.partOf|**Encounter.location (MS)**| |Immunization|Yes|No|Immunization.encounter|Immunization.location| |MedicationDispense|Yes|No|MedicationDispense.context|MedicationDispense.location| |Observation (Lab)|Yes|No|Observation.encounter|Not included - potential extension| |PractitionerRole|No|||| |Procedure|Yes||Procedure.encounter|Procedure.location| |Provenance|No|||| |ServiceRequest|Yes||ServiceRequest.encounter|ServiceRequest.locationCode</br>ServiceRequest.locationReference| |Specimen|Yes||Not included|Not included| #### C-CDA |C-CDA Template|Appropriate|Any current Constraints|Location|Note| |---|---|---|---|---| |Result Observation (covers labs and rads)|Yes|No|Add Service Delivery Location|SDLOC vocab| |Encounter Activity|Yes|Yes|Service Delivery Location|SDLOC vocab| |Planned Encounter|Yes|Yes|Service Delivery Location|SDLOC vocab| |Immunization Activity|Yes|No|Add Service Delivery Location|SDLOC vocab| |Medication Dispense|Yes|No|Add Service Delivery Location|SDLOC vocab| |Procedure Activity Procedure|Yes|Yes|Service Delivery Location|SDLOC vocab| |Planned Procedure|Yes|No|Add Service Delivery Location|SDLOC vocab| |Specimen Observation|Yes|No|Add Service Delivery Location|SDLOC vocab| ### Decisions 1. Add :new: fields US Core Location Profile (see table) 3. To support links to the facility via Encounteradd .encounter MS (.context for Med Dispense) to the Profiles listed below to support links to the facility via Encounter which references a location. - in addition add .location to to the Immunization Profile - add implementer guidance that if the actual event location != to Encounter.location SHOULD use the .location to clarify. Note: Current Must Support/USCDI Requirements are listed in **bold** text |US Core Resource|Reference to Encounter|Reference to Location |--- |--- |--- | |DiagnosticReport (Lab)|DiagnosticReport.encounter|None| |DiagnosticReport (Notes)|**DiagnosticReport.encounter (MS)**|None| |Encounter|Encounter.partOf|**Encounter.location (MS)**| |Immunization|Immunization.encounter|Immunization.location| |MedicationDispense|MedicationDispense.context|MedicationDispense.location| |Observation (Lab)|Observation.encounter|Not included - potential extension| |Procedure|Procedure.encounter|Procedure.location| |ServiceRequest|ServiceRequest.encounter|ServiceRequest.locationCode</br>ServiceRequest.location ### :arrow_right: [Location Profile and Examples](https://healthedata1.github.io/USCDI4-Sandbox/artifacts.html#facility_information) ### IG Updates - [ ] USCDI Mapping Table - [ ] Update US Core Profile - [ ] Update Example(s) - [ ] Update USCDI Conformance Section ---