PACIO Personal Functioning and Engagement Implementation Guide
2.0.0-ballot - STU2 Ballot United States of America flag

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-ballot 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

CapabilityStatement: Personal Functioning and Engagement Capability Statement

Official URL: http://hl7.org/fhir/us/pacio-pfe/CapabilityStatement/pacio-pfe-cap Version: 2.0.0-ballot
Draft as of 2022-08-12 Computable Name: Personal_Functioning_And_Engagement_CapabilityStatement

This Capability Statement defines the expected capabilities of a Personal Functioning and Engagement FHIR server conforming to the Personal Functioning and Engagement Implementation Guide.

Raw OpenAPI-Swagger Definition file | Download

Generated Narrative: CapabilityStatement pacio-pfe-cap

Personal Functioning and Engagement Capability Statement

  • Implementation Guide Version: 2.0.0-ballot
  • FHIR Version: 4.0.1
  • Supported Formats: xml, json
  • Supported Patch Formats:
  • Published on: 2022-08-12 00:00:00+0000
  • Published by: HL7 International / Patient Care

Note to Implementers: FHIR Capabilities

Any FHIR capability may be 'allowed' by the system unless explicitly marked as 'SHALL NOT'. A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.

FHIR RESTful Capabilities

Mode: server

The PFE Server SHALL:

  1. Support all profiles defined in this Implementation Guide.
  2. Implement the RESTful behavior according to the FHIR specification.
  3. Return the following response classes:
    • (Status 400): invalid parameter
    • (Status 401/4xx): unauthorized request
    • (Status 403): insufficient scope
    • (Status 404): unknown resource
    • (Status 410): deleted resource.
  4. Support json source formats for all PFE interactions.
  5. Support the searchParameters on each profile individually and in combination.

The PFE Server SHOULD:

  1. Support xml source formats for all PFE interactions.
Security
  1. See the Guidance section for requirements and recommendations.
  2. A server SHALL reject any unauthorized requests by returning an HTTP 401 "Unauthorized", HTTP 403 "Forbidden", or HTTP 404 "Not Found" response code.
Summary of System-wide Interactions
  • MAYSupports the batchinteraction.
  • MAYSupports the search-systeminteraction.

Capabilities by Resource/Profile

Summary

The summary table lists the resources that are part of this configuration, and for each resource it lists:

  • The relevant profiles (if any)
  • The interactions supported by each resource (Read, Search, Update, and Create, are always shown, while VRead, Patch, Delete, History on Instance, or History on Type are only present if at least one of the resources has support for them.
  • The required, recommended, and some optional search parameters (if any).
  • The linked resources enabled for _include
  • The other resources enabled for _revinclude
  • The operations on the resource (if any)
Resource TypeProfileRV-RSUPCDH-IH-TSearches_include_revincludeOperations
ObservationSupported Profiles
  Personal Functioning and Engagement Clinical Test Observationversion: {0}2.0.0-ballot)
  Personal Functioning and Engagement Collectionversion: {0}2.0.0-ballot)
  Personal Functioning and Engagement Single Observationversion: {0}2.0.0-ballot)
yyyyyyyyydate, combo-data-absent-reason, code, combo-code-value-quantity, subject, component-data-absent-reason, value-concept, value-date, code-value-string, component-code-value-quantity, based-on, code-value-date, patient, specimen, component-code, code-value-quantity, combo-code-value-concept, value-string, identifier, performer, combo-code, method, value-quantity, component-value-quantity, data-absent-reason, combo-value-quantity, encounter, code-value-concept, component-code-value-concept, component-value-concept, category, device, combo-value-concept, statusObservation.subject, Observation.based-on, Observation.patient, Observation.specimen, Observation.context, Observation.performer, Observation.encounter, Observation.deviceChargeItem.service, ClinicalImpression.finding-ref, ClinicalImpression.investigation, DiagnosticReport.result, Immunization.reaction, ImmunizationRecommendation.information, MedicationStatement.part-of, Procedure.part-of, QuestionnaireResponse.parent
DiagnosticReportSupported Profiles
  Personal Functioning and Engagement Narrative History of Statusversion: {0}2.0.0-ballot)
yyyyyyyyydate, code, patient, identifier, encounterDiagnosticReport.based-on, DiagnosticReport.subject, DiagnosticReport.patient, DiagnosticReport.encounter, DiagnosticReport.media, DiagnosticReport.performer, DiagnosticReport.result, DiagnosticReport.results-interpreter, DiagnosticReport.specimen
DeviceUseStatementSupported Profiles
  Personal Functioning and Engagement Use of Deviceversion: {0}2.0.0-ballot)
yyyyyyyyyidentifier, subject, patient, deviceDeviceUseStatement.subject, DeviceUseStatement.patient, DeviceUseStatement.device
ConditionSupported Profiles
  Personal Functioning and Engagement Condition Encounter Diagnosis Profileversion: {0}2.0.0-ballot)
  Personal Functioning and Engagement Condition Problems and Health Concerns Profileversion: {0}2.0.0-ballot)
yyyyyyyyyidentifier, subject, bodySite, asserter, recordedDate, code, encounterCondition.identifier, Condition.subject, Condition.bodySite, Condition.asserter, recordedDate, code, encounter
GoalSupported Profiles
  Personal Functioning and Engagement Goal Profileversion: {0}2.0.0-ballot)
yyyyyyyyyidentifier, subject, patient, achievementStatus, addressesGoal.identifier, Goal.subject, Goal.patient, Goal.achievementStatus, Goal.addresses
NutritionOrderSupported Profiles
  Personal Functioning and Engagement Nutrition Order Profileversion: {0}2.0.0-ballot)
yyyyyyyyyidentifier, subject, patient, encounter, orderer, statusNutritionOrder.identifier, NutritionOrder.subject, NutritionOrder.patient, NutritionOrder.encounter, NutritionOrder.orderer, NutritionOrder.status
ServiceRequestSupported Profiles
  Personal Functioning and Engagement Service Request Profileversion: {0}2.0.0-ballot)
yyyyyyyyyidentifier, subject, patient, status, code, requester, performer, reason referenceServiceRequest.identifier, ServiceRequest.subject, ServiceRequest.patient, ServiceRequest.status, ServiceRequest.code, ServiceRequest.requester, ServiceRequest.performer, ServiceRequest.reasonReference

Resource Conformance: SHALL Observation

Core FHIR Resource
Observation
Reference Policy
literal, logical
Interaction summary
  • SHALLsupport create, update, read, search-type.
  • SHOULDsupport vread, history-instance.
  • MAYsupport delete, history-type, patch.

Search Parameters
ConformanceParameterTypeDocumentation
MAYdatedate

Obtained date/time. If the obtained element is a period, a date that falls in the period

MAYcombo-data-absent-reasontoken

The reason why the expected value in the element Observation.value[x] or Observation.component.value[x] is missing.

MAYcodetoken

The code of the observation type

MAYcombo-code-value-quantitycomposite

Code and quantity value parameter pair, including in components

MAYsubjectreference

The subject that the observation is about

MAYcomponent-data-absent-reasontoken

The reason why the expected value in the element Observation.component.value[x] is missing.

MAYvalue-concepttoken

The value of the observation, if the value is a CodeableConcept

MAYvalue-datedate

The value of the observation, if the value is a date or period of time

MAYcode-value-stringcomposite

Code and string value parameter pair

MAYcomponent-code-value-quantitycomposite

Component code and component quantity value parameter pair

MAYbased-onreference

Reference to the test or procedure request.

MAYcode-value-datecomposite

Code and date/time value parameter pair

MAYpatientreference

The subject that the observation is about (if patient)

MAYspecimenreference

Specimen used for this observation

MAYcomponent-codetoken

The component code of the observation type

MAYcode-value-quantitycomposite

Code and quantity value parameter pair

MAYcombo-code-value-conceptcomposite

Code and coded value parameter pair, including in components

MAYvalue-stringstring

The value of the observation, if the value is a string, and also searches in CodeableConcept.text

MAYidentifiertoken

The unique id for a particular observation

MAYperformerreference

Who performed the observation

MAYcombo-codetoken

The code of the observation type or component type

MAYmethodtoken

The method used for the observation

MAYvalue-quantityquantity

The value of the observation, if the value is a Quantity, or a SampledData (just search on the bounds of the values in sampled data)

MAYcomponent-value-quantityquantity

The value of the component observation, if the value is a Quantity, or a SampledData (just search on the bounds of the values in sampled data)

MAYdata-absent-reasontoken

The reason why the expected value in the element Observation.value[x] is missing.

MAYcombo-value-quantityquantity

The value or component value of the observation, if the value is a Quantity, or a SampledData (just search on the bounds of the values in sampled data)

MAYencounterreference

Encounter related to the observation

MAYcode-value-conceptcomposite

Code and coded value parameter pair

MAYcomponent-code-value-conceptcomposite

Component code and component coded value parameter pair

MAYcomponent-value-concepttoken

The value of the component observation, if the value is a CodeableConcept

MAYcategorytoken

The classification of the type of observation

MAYdevicereference

The Device that generated the observation data.

MAYcombo-value-concepttoken

The value or component value of the observation, if the value is a CodeableConcept

MAYstatustoken

The status of the observation

 

Resource Conformance: MAY DiagnosticReport

Core FHIR Resource
DiagnosticReport
Reference Policy
literal, logical
Interaction summary
  • SHALLsupport create, update, read, search-type.
  • SHOULDsupport vread, history-instance.
  • MAYsupport delete, history-type, patch.

Search Parameters
ConformanceParameterTypeDocumentation
SHALLpatientreference

The subject that the report is about (if patient)

MAYdatedate

Obtained date/time. If the obtained element is a period, a date that falls in the period

MAYcodetoken

The code of the report type

MAYidentifiertoken

The unique id for a particular report

MAYencounterreference

Encounter related to the report

 

Resource Conformance: SHOULD DeviceUseStatement

Core FHIR Resource
DeviceUseStatement
Reference Policy
literal, logical
Interaction summary
  • SHOULDsupport create, update, delete, read.
  • MAYsupport vread, history-instance, history-type, search-type, patch.

Search Parameters
ConformanceParameterTypeDocumentation
MAYidentifiertoken

Search by identifier

MAYsubjectreference

Search by subject

MAYpatientreference

Search by subject - a patient

MAYdevicereference

Search by device

 

Resource Conformance: SHOULD Condition

Core FHIR Resource
Condition
Reference Policy
literal, logical
Interaction summary
  • SHOULDsupport create, update, delete, read.
  • MAYsupport vread, history-instance, history-type, search-type, patch.

Search Parameters
ConformanceParameterTypeDocumentation
MAYidentifiertoken

Search by identifier

MAYsubjectreference

Search by subject

MAYbodySitetoken

Search by body site

MAYasserterreference

Search by asserter

MAYrecordedDatetoken

Search by recorded date

MAYcodetoken

Search by code

MAYencounterreference

Search by encounter

 

Resource Conformance: SHOULD Goal

Core FHIR Resource
Goal
Reference Policy
literal, logical
Interaction summary
  • SHOULDsupport create, update, delete, read.
  • MAYsupport vread, history-instance, history-type, search-type, patch.

Search Parameters
ConformanceParameterTypeDocumentation
MAYidentifiertoken

Search by identifier

MAYsubjectreference

Search by subject

MAYpatientreference

Search by subject - a patient

MAYachievementStatustoken

Search by achievement status

MAYaddressesreference

Search by addresses

 

Resource Conformance: SHOULD NutritionOrder

Core FHIR Resource
NutritionOrder
Reference Policy
literal, logical
Interaction summary
  • SHOULDsupport create, update, delete, read.
  • MAYsupport vread, history-instance, history-type, search-type, patch.

Search Parameters
ConformanceParameterTypeDocumentation
MAYidentifiertoken

Search by identifier

MAYsubjectreference

Search by subject

MAYpatientreference

Search by subject - a patient

MAYencounterreference

Search by encounter

MAYordererreference

Search by orderer

MAYstatusreference

Search by status

 

Resource Conformance: SHOULD ServiceRequest

Core FHIR Resource
ServiceRequest
Reference Policy
literal, logical
Interaction summary
  • SHOULDsupport create, update, delete, read.
  • MAYsupport vread, history-instance, history-type, search-type, patch.

Search Parameters
ConformanceParameterTypeDocumentation
MAYidentifiertoken

Search by identifier

MAYsubjectreference

Search by subject

MAYpatientreference

Search by subject - a patient

MAYstatustoken

Search by status

MAYcodetoken

Search by code

MAYrequesterreference

Search by requester

MAYperformerreference

Search by performer

MAYreason referencereference

Search by reason reference