Swedish Healthcare Service - Health Condition Description
0.1.0 - CI Build Sweden

Swedish Healthcare Service - Health Condition Description - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

GetFunctionalStatus

GetFunctionalStatus Service

Overview

Service Name: GetFunctionalStatus
Version: 2.0
Domain: clinicalprocess:healthcond:description
Purpose: Retrieves functional status assessments for a patient

Description

The GetFunctionalStatus service provides access to functional status assessments including ADL (Activities of Daily Living), PADL (Personal ADL), mobility assessments, cognitive assessments, and other functional evaluations registered for a patient in Swedish healthcare systems.

Service Interface

Request Parameters

The service accepts the following parameters to filter and retrieve functional status assessments:

Parameter Cardinality Type Description
patientId 1..1 PatientId Required. Patient identifier (personnummer or samordningsnummer, 12 characters without separator)
careUnitHSAId 0..* string Filter results to specific care units using HSA-ID
timePeriod 0..1 TimePeriod Limit search to assessments within a specific time period
sourceSystemHSAId 0..1 string Filter to specific source system
careContactId 0..* string Filter to specific care contacts
assessmentType 0..* CodedValue Filter by assessment type (ADL, PADL, mobility, etc.)

Response Structure

The service returns zero or more functional status assessments matching the request criteria. Each assessment contains:

  • Assessment Header: Metadata about the assessment (document ID, source system, patient ID, accountable professional)
  • Assessment Body: The actual assessment information including assessment type, scores, observations, and evaluations
  • Legal Authenticator (optional): Information about who signed/authenticated the assessment

See the Logical Models for complete structure definitions.

Assessment Types

Common functional status assessment types include:

  • ADL (Activities of Daily Living): Basic self-care activities
  • PADL (Personal Activities of Daily Living): Personal hygiene and grooming
  • IADL (Instrumental Activities of Daily Living): Complex tasks like cooking, managing finances
  • Mobility Assessment: Walking, transfers, balance
  • Cognitive Assessment: Memory, orientation, decision-making
  • Pain Assessment: Pain levels and characteristics
  • Fall Risk Assessment: Risk factors for falls
  • Nutrition Assessment: Nutritional status and needs

Business Rules

  1. Patient Identification: Patient must be identified using valid Swedish personnummer or samordningsnummer
  2. Time Period: If specified, only assessments with validity periods overlapping the search period are returned
  3. Assessment Type Filter: If specified, only assessments of the specified types are returned
  4. Legitimate Relationship: Healthcare professional must have a legitimate relationship to access patient data
  5. Audit Logging: All access is logged for security audit purposes

Use Cases

Primary Use Case: Retrieve All Functional Assessments

Healthcare professional needs to see all functional status assessments for a patient to understand their care needs.

Request Example:

patientId: 191212121212
patientId.type: 1.2.752.129.2.1.3.1 (Swedish personnummer)

Use Case: Retrieve Recent ADL Assessments

Retrieve ADL assessments from the last 6 months.

Request Example:

patientId: 191212121212
timePeriod.start: 20240601
timePeriod.end: 20241231
assessmentType.code: ADL

Use Case: Retrieve Assessments for Care Planning

Retrieve all functional assessments to support care planning.

Request Example:

patientId: 191212121212
careUnitHSAId: SE2321000016-1234
assessmentType: [ADL, PADL, Mobility]

Data Quality Requirements

  • Assessment types must be coded according to approved code systems
  • Each assessment must have an accountable healthcare professional
  • Document ID must be unique within the source system
  • Time stamps must be in YYYYMMDDHHmmss format
  • Assessment scores and observations must be documented according to standardized scales when applicable

Interaction Flow

The GetFunctionalStatus service follows the standard request-response pattern:

Consumer                    Aggregator/Producer
   |                               |
   |--- GetFunctionalStatus ------>|
   |      (SOAP Request)            |
   |                               |
   |<------ Response --------------|
   |   (Assessment Collection)     |
   |                               |

When using an aggregator with multiple source systems:

Consumer          Aggregator           EI          Source Systems
   |                  |                 |              |
   |-- GetFunc ------->|                 |              |
   |                  |-- Query EI ---->|              |
   |                  |<- HSA-IDs ------|              |
   |                  |                                |
   |                  |--------- Parallel Queries ---->|
   |                  |                 |         Care System
   |                  |                 |         Social Care
   |                  |<-------- Responses ------------|
   |                  |                 |              |
   |<- Aggregated ----|                 |              |
   |    Response      |                 |              |

Message Examples

Request Example - ADL Assessment

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
               xmlns:add="http://www.w3.org/2005/08/addressing"
               xmlns:ns="urn:riv:clinicalprocess:healthcond:description:GetFunctionalStatusResponder:2">
  <soap:Header>
    <add:To>https://aggregator.example.se/GetFunctionalStatus/2</add:To>
    <add:Action>urn:riv:clinicalprocess:healthcond:description:GetFunctionalStatusResponder:2:GetFunctionalStatus</add:Action>
    <add:MessageID>urn:uuid:34567890-3456-3456-3456-345678901cde</add:MessageID>
    <urn:LogicalAddress xmlns:urn="urn:riv:itintegration:registry:1">SE2321000016-1234</urn:LogicalAddress>
  </soap:Header>
  <soap:Body>
    <ns:GetFunctionalStatus>
      <ns:patientId>
        <ns:id>195005051234</ns:id>
        <ns:type>1.2.752.129.2.1.3.1</ns:type>
      </ns:patientId>
      <ns:timePeriod>
        <ns:start>20240601</ns:start>
        <ns:end>20241231</ns:end>
      </ns:timePeriod>
      <ns:assessmentType>
        <ns:code>ADL</ns:code>
        <ns:codeSystem>1.2.752.129.2.2.1.90</ns:codeSystem>
        <ns:displayName>Activities of Daily Living</ns:displayName>
      </ns:assessmentType>
    </ns:GetFunctionalStatus>
  </soap:Body>
</soap:Envelope>

Response Example - ADL Assessment Result

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
               xmlns:ns="urn:riv:clinicalprocess:healthcond:description:GetFunctionalStatusResponder:2">
  <soap:Body>
    <ns:GetFunctionalStatusResponse>
      <ns:result>
        <ns:resultCode>OK</ns:resultCode>
        <ns:message>Successfully retrieved 1 functional status assessment</ns:message>
      </ns:result>
      <ns:functionalStatus>
        <ns:functionalStatusHeader>
          <ns:documentId>func-789-2024</ns:documentId>
          <ns:sourceSystemHSAId>SE2321000016-5678</ns:sourceSystemHSAId>
          <ns:documentTime>20241015100000</ns:documentTime>
          <ns:patientId>
            <ns:id>195005051234</ns:id>
            <ns:type>1.2.752.129.2.1.3.1</ns:type>
          </ns:patientId>
          <ns:accountableHealthcareProfessional>
            <ns:healthcareProfessionalHSAId>SE2321000016-C789</ns:healthcareProfessionalHSAId>
            <ns:healthcareProfessionalName>Sjuksköterska Carin Carlsson</ns:healthcareProfessionalName>
            <ns:healthcareProfessionalCareUnitHSAId>SE2321000016-5678</ns:healthcareProfessionalCareUnitHSAId>
          </ns:accountableHealthcareProfessional>
        </ns:functionalStatusHeader>
        <ns:functionalStatusBody>
          <ns:assessmentType>
            <ns:code>ADL</ns:code>
            <ns:codeSystem>1.2.752.129.2.2.1.90</ns:codeSystem>
            <ns:displayName>Activities of Daily Living</ns:displayName>
          </ns:assessmentType>
          <ns:assessmentDate>20241015</ns:assessmentDate>
          <ns:validityTimePeriod>
            <ns:start>20241015</ns:start>
          </ns:validityTimePeriod>
          <ns:assessmentResult>
            <ns:assessmentComponent>
              <ns:componentType>
                <ns:code>BATHING</ns:code>
                <ns:displayName>Tvättning/dusch</ns:displayName>
              </ns:componentType>
              <ns:score>3</ns:score>
              <ns:interpretation>Behöver viss hjälp med duschning</ns:interpretation>
            </ns:assessmentComponent>
            <ns:assessmentComponent>
              <ns:componentType>
                <ns:code>DRESSING</ns:code>
                <ns:displayName>Påklädning</ns:displayName>
              </ns:componentType>
              <ns:score>4</ns:score>
              <ns:interpretation>Självständig med påklädning</ns:interpretation>
            </ns:assessmentComponent>
            <ns:assessmentComponent>
              <ns:componentType>
                <ns:code>TOILETING</ns:code>
                <ns:displayName>Toalettbesök</ns:displayName>
              </ns:componentType>
              <ns:score>3</ns:score>
              <ns:interpretation>Behöver viss hjälp med toalettbesök</ns:interpretation>
            </ns:assessmentComponent>
          </ns:assessmentResult>
          <ns:overallAssessment>Patient är i huvudsak självständig men behöver viss hjälp med hygien. Rekommenderar fortsatt hemtjänststöd.</ns:overallAssessment>
        </ns:functionalStatusBody>
      </ns:functionalStatus>
    </ns:GetFunctionalStatusResponse>
  </soap:Body>
</soap:Envelope>

Error Handling

The service may return the following error conditions:

  • Patient not found: No patient with the specified ID exists
  • No assessments found: Patient exists but no assessments match the search criteria
  • Access denied: Healthcare professional lacks legitimate relationship
  • Invalid input: Request parameters are malformed or invalid

Technical Notes

  • Endpoint Pattern: /clinicalprocess/healthcond/description/GetFunctionalStatus/2
  • Protocol: HTTPS
  • Message Format: XML (SOAP envelope)
  • Character Encoding: UTF-8