PACIO Personal Functioning and Engagement Implementation Guide, published by HL7 International / Patient Care. This guide is not an authorized publication; it is the continuous build for version 2.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-pacio-pfe/ and changes regularly. See the Directory of published versions

Formal Specification

Page standards status: Informative

Highlight text changes?

This section defines additional requirements and guidance relevant to this IG as a whole. The FHIR Conformance Rules define the conformance verbs - SHALL, SHOULD, MAY - used in this IG.

Claiming Conformance to a Personal Functioning and Engagement Profile

To claim conformance to a Profile in this IG, servers SHALL:

• Be able to populate all Profile data elements that have a minimum cardinality >= 1 and/or flagged as Must Support as defined by that profile’s StructureDefinition.
• Conform to the Personal Functioning and Engagement Capability Statement expectations for that Profile’s type.

Must Support

The following rules apply to all Personal Functioning and Engagement Profile elements marked as Must Support. Must Support on any profile data element SHALL be interpreted as follows:

Data Source System Requirements

• Data Sources Systems SHALL be capable of populating all data elements as part of the query results as specified by the Personal Functioning and Engagement Capability Statement.

Data Consumer System Requirements

• Data Consumer Systems SHALL be capable of displaying the data elements for human use.
• Data Consumer Systems SHOULD be capable of storing the data elements for other uses (such as record keeping of data used for clinical use).
• Data Consumer Systems SHALL be capable of processing resource instances containing the data element without generating an error or causing the application to fail.
• Data Consumer Systems SHALL interpret missing data elements within resources instances as not being present on the Data Sources system’s or as being withheld for privacy or business reasons.

Profiles used by this IG, but defined in other IGs, inherit the definition of Must Support from their respective guides.

Use of ConceptMap for ICF Domain Categorization

When a LOINC code is known for an observation, systems SHOULD use the LOINC to ICF Mapping to populate the PFEDomain category slice with the appropriate ICF code(s). This applies to the following profiles:

• Personal Functioning and Engagement Single Observation
• Personal Functioning and Engagement Clinical Test Observation
• Personal Functioning and Engagement Collection

If a LOINC code maps to multiple ICF codes within the ConceptMap, all mapped ICF codes SHOULD be included as separate repetitions within the PFEDomain category slice.