This page is part of the PACIO Personal Functioning and Engagement Implementation Guide (v1.0.0: STU 1) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions
Official URL: http://hl7.org/fhir/us/pacio-pfe/ValueSet/pfe-example-obs-vs | Version: 1.0.0 | |||
Draft as of 2024-01-05 | Computable Name: PFEExampleObservationsVS | |||
Copyright/Legal: This material contains content from LOINC (http://loinc.org). LOINC is copyright © 1995-2020, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license at http://loinc.org/license. LOINC® is a registered United States trademark of Regenstrief Institute, Inc. |
This value set includes LOINC codes that provide examples of observations within the scope of the Personal Functioning and Engagement IG.
References
The entries in this value set are examples of the codes expected to be used on Observation instances within the scope of this Personal Functioning and Engagement Implementation Guide (PFE IG). It is used only within the Abstract PFE Observation that serves to show the requirements placed on Observations by the PFE IG separate from requirements put in place by US Core profiles. That profile is not expected to be implemented and is included only for informational purposes and clarity. Implementers should follow guidance around the use of codes on the domains page and within specific implementable profiles.
Codes in this value set are intended to cover different types and flavors of observations covered by this IG. The codes included are pulled from
*Panels and groupers are not in scope for inclusion within domain-based value sets within STU1 of the PFE IG. However, implementers may still create observation instances using these codes as a part of following the recommended structure for representing complex assessments. Therefore, they are included here as examples even though they will not be found within the domain-based value sets.
http://loinc.org
Code | Display |
101265-7 | MDS v3.0 - RAI v1.18.11 - Functional Abilities and Goals - Admission [CMS Assessment] |
95019-6 | Eating - usual functional ability during assessment period [CMS Assessment] |
79532-8 | Daily activity score [AM-PAC] |
99828-6 | Functional Communication Measure - Multi-Modal Functional Communication panel [ASHA NOMS] |
99831-0 | Frequency of conveying meaningful complex messages in low demand situations |
99835-1 | Functional Communication Measure - Multi-Modal Functional Communication score [ASHA NOMS] |
91375-6 | Hearing threshold Ear - left --250 Hz |
Expansion based on:
This value set contains 7 concepts
Code | System | Display |
101265-7 | http://loinc.org | MDS v3.0 - RAI v1.18.11 - Functional Abilities and Goals - Admission [CMS Assessment] |
95019-6 | http://loinc.org | Eating - usual functional ability during assessment period [CMS Assessment] |
79532-8 | http://loinc.org | Daily activity score [AM-PAC] |
99828-6 | http://loinc.org | Functional Communication Measure - Multi-Modal Functional Communication panel [ASHA NOMS] |
99831-0 | http://loinc.org | Frequency of conveying meaningful complex messages in low demand situations |
99835-1 | http://loinc.org | Functional Communication Measure - Multi-Modal Functional Communication score [ASHA NOMS] |
91375-6 | http://loinc.org | Hearing threshold Ear - left --250 Hz |
Explanation of the columns that may appear on this page:
Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
System | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
Code | The code (used as the code in the resource instance) |
Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
Definition | An explanation of the meaning of the concept |
Comments | Additional notes about how to use the code |