My FHIR Client Capability Statement

復健訓練評估量表實作指引(Rehabilitation Training Scale Implementation Guide), published by Kimsber. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/Kimsber/Rehab-IG/ and changes regularly. See the Directory of published versions

CapabilityStatement: My FHIR Client Capability Statement

Official URL: https://build.fhir.org/ig/Kimsber/Rehab-IG/CapabilityStatement/MyFHIRClientCapabilityStatement				Version: 0.1.0
Active as of 2025-10-25				Computable Name: MyFHIRClientCapabilityStatement

此 CapabilityStatement 定義了用戶端（Client）應支援的 FHIR RESTful API 功能。用戶端建議應該（SHOULD）使用伺服端能力聲明中的查詢參數，支援讀取和查詢一個或多個 FHIR Profile。

Raw OpenAPI-Swagger Definition file | Download

Implementation Guide Version: 0.1.0
FHIR Version: 4.0.1
Supported Formats: json, xml
Supported Patch Formats: application/json-patch+json
Published on: 2025-10-25
Published by: Kimsber

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: `client`

用戶端建議應該（SHOULD）使用伺服端能力聲明中的查詢參數，支援讀取和查詢一個或多個 Profile。系統互動能力：可能可以（MAY）支援交易（transaction）、批次（batch）與查詢系統（search-system）。

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 Type	Profile	R	S	U	C	Searches	Operations
Bundle	https://github.com/Kimsber/StructureDefinition/Bundle	Y	Y			_id, identifier
CarePlan	https://github.com/Kimsber/StructureDefinition/CarePlan	Y	Y			patient, category, date, status
Condition	https://github.com/Kimsber/fhir/StructureDefinition/Condition	Y	Y			_id, clinical-status, code, subject, onset-date, abatement-date, severity
Encounter	https://github.com/Kimsber/StructureDefinition/Encounter	Y	Y			_id, class, date, identifier, location, subject, status
Goal	https://github.com/Kimsber/StructureDefinition/Goal	Y	Y			patient, lifecycle-status, target-date, description
MedicationAdministration	https://github.com/Kimsber/StructureDefinition/MedicationAdministration	Y	Y			code, identifier, medication, patient, status, context, device, effective-time, performer, reason-given, reason-not-given, request, subject
Observation	https://github.com/Kimsber/StructureDefinition/Observation	Y	Y			_id, category, code, date, performer, status, subject, patient, _lastUpdated
Organization	https://github.com/Kimsber/StructureDefinition/Organization	Y	Y			_id, identifier, name, type
Patient	https://github.com/Kimsber/StructureDefinition/Patient	Y	Y			_id, birthdate, gender, identifier, name	`$everything`
Practitioner	https://github.com/Kimsber/StructureDefinition/Practitioner	Y	Y			_id, identifier, name
PractitionerRole	https://github.com/Kimsber/StructureDefinition/PractitionerRole	Y	Y			_id, identifier, specialty
Procedure	https://github.com/Kimsber/StructureDefinition/Procedure	Y	Y			_id, code, status, subject, date
Questionnaire	https://github.com/Kimsber/StructureDefinition/Questionnaire	Y	Y			identifier, title
QuestionnaireResponse	https://build.fhir.org/ig/Kimsber/Rehab-IG/StructureDefinition/QuestionnaireResponse	Y	Y	Y	Y	_id, patient, status, authored, questionnaire, subject	`$extract`

Resource Conformance: SHOULDBundle

Base System Profile
https://github.com/Kimsber/StructureDefinition/Bundle

Profile Conformance
SHOULD

Reference Policy

Interaction summary

SHOULD support read, search-type.

Search Parameters

Conformance	Parameter	Type	Documentation
SHOULD	_id	`token`
SHOULD	identifier	`token`

Resource Conformance: SHOULDCarePlan

Base System Profile
https://github.com/Kimsber/StructureDefinition/CarePlan

Profile Conformance
SHOULD

Reference Policy

Interaction summary

SHOULD support read, search-type.

Search Parameters

Conformance	Parameter	Type
SHOULD	patient	`reference`
SHOULD	category	`token`
SHOULD	date	`date`
SHOULD	status	`token`

Resource Conformance: SHOULDCondition

Base System Profile
https://github.com/Kimsber/fhir/StructureDefinition/Condition

Profile Conformance
SHOULD

Reference Policy

Interaction summary

SHOULD support read, search-type.

Search Parameters

Conformance	Parameter	Type
SHOULD	_id	`token`
SHOULD	clinical-status	`token`
SHOULD	code	`token`
SHOULD	subject	`reference`
SHOULD	onset-date	`date`
SHOULD	abatement-date	`date`
SHOULD	severity	`token`

Resource Conformance: SHOULDEncounter

Base System Profile
https://github.com/Kimsber/StructureDefinition/Encounter

Profile Conformance
SHOULD

Reference Policy

Interaction summary

SHOULD support read, search-type.

Search Parameters

Conformance	Parameter	Type
SHOULD	_id	`token`
SHOULD	class	`token`
SHOULD	date	`date`
SHOULD	identifier	`token`
SHOULD	location	`reference`
SHOULD	subject	`reference`
SHOULD	status	`token`

Resource Conformance: SHOULDGoal

Base System Profile
https://github.com/Kimsber/StructureDefinition/Goal

Profile Conformance
SHOULD

Reference Policy

Interaction summary

SHOULD support read, search-type.

Search Parameters

Conformance	Parameter	Type
SHOULD	patient	`reference`
SHOULD	lifecycle-status	`token`
SHOULD	target-date	`date`
SHOULD	description	`token`

Resource Conformance: SHOULDMedicationAdministration

Base System Profile
https://github.com/Kimsber/StructureDefinition/MedicationAdministration

Profile Conformance
SHOULD

Reference Policy

Interaction summary

SHOULD support read, search-type.

Search Parameters

Conformance	Parameter	Type
SHOULD	code	`token`
SHOULD	identifier	`token`
SHOULD	medication	`reference`
SHOULD	patient	`reference`
SHOULD	status	`token`
SHOULD	context	`reference`
SHOULD	device	`reference`
SHOULD	effective-time	`date`
SHOULD	performer	`reference`
SHOULD	reason-given	`token`
SHOULD	reason-not-given	`token`
SHOULD	request	`reference`
SHOULD	subject	`reference`

Resource Conformance: SHOULDObservation

Base System Profile
https://github.com/Kimsber/StructureDefinition/Observation

Profile Conformance
SHOULD

Reference Policy

Interaction summary

SHOULD support read, search-type.

Search Parameters

Conformance	Parameter	Type
SHOULD	_id	`token`
SHOULD	category	`token`
SHOULD	code	`token`
SHOULD	date	`date`
SHOULD	performer	`reference`
SHOULD	status	`token`
SHOULD	subject	`reference`
SHOULD	patient	`reference`
SHOULD	_lastUpdated	`date`

Resource Conformance: SHOULDOrganization

Base System Profile
https://github.com/Kimsber/StructureDefinition/Organization

Profile Conformance
SHOULD

Reference Policy

Interaction summary

SHOULD support read, search-type.

Search Parameters

Conformance	Parameter	Type
SHOULD	_id	`token`
SHOULD	identifier	`token`
SHOULD	name	`string`
SHOULD	type	`token`

Resource Conformance: SHOULDPatient

Base System Profile
https://github.com/Kimsber/StructureDefinition/Patient

Profile Conformance
SHOULD

Reference Policy

Interaction summary

SHOULD support read, search-type.

Search Parameters

Conformance	Parameter	Type
SHOULD	_id	`token`
SHOULD	birthdate	`date`
SHOULD	gender	`token`
SHOULD	identifier	`token`
SHOULD	name	`string`

Extended Operations

Conformance	Operation	Documentation
SHOULD	$everything

Resource Conformance: SHOULDPractitioner

Base System Profile
https://github.com/Kimsber/StructureDefinition/Practitioner

Profile Conformance
SHOULD

Reference Policy

Interaction summary

SHOULD support read, search-type.

Search Parameters

Conformance	Parameter	Type
SHOULD	_id	`token`
SHOULD	identifier	`token`
SHOULD	name	`string`

Resource Conformance: SHOULDPractitionerRole

Base System Profile
https://github.com/Kimsber/StructureDefinition/PractitionerRole

Profile Conformance
SHOULD

Reference Policy

Interaction summary

SHOULD support read, search-type.

Search Parameters

Conformance	Parameter	Type
SHOULD	_id	`token`
SHOULD	identifier	`token`
SHOULD	specialty	`token`

Resource Conformance: SHOULDProcedure

Base System Profile
https://github.com/Kimsber/StructureDefinition/Procedure

Profile Conformance
SHOULD

Reference Policy

Interaction summary

SHOULD support read, search-type.

Search Parameters

Conformance	Parameter	Type
SHOULD	_id	`token`
SHOULD	code	`token`
SHOULD	status	`token`
SHOULD	subject	`reference`
SHOULD	date	`date`

Resource Conformance: SHOULDQuestionnaire

Base System Profile
https://github.com/Kimsber/StructureDefinition/Questionnaire

Profile Conformance
SHOULD

Reference Policy

Interaction summary

SHOULD support read, search-type.

Search Parameters

Conformance	Parameter	Type	Documentation
SHOULD	identifier	`token`
SHOULD	title	`string`

Resource Conformance: SHOULDQuestionnaireResponse

Base System Profile
https://build.fhir.org/ig/Kimsber/Rehab-IG/StructureDefinition/QuestionnaireResponse

Profile Conformance
SHOULD

Reference Policy

Interaction summary

SHOULD support read, search-type, create, update.

Search Parameters

Conformance	Parameter	Type
SHOULD	_id	`token`
SHOULD	patient	`reference`
SHOULD	status	`token`
SHOULD	authored	`date`
SHOULD	questionnaire	`reference`
SHOULD	subject	`reference`

Extended Operations

Conformance	Operation	Documentation
SHOULD	$extract	用戶端應支援 $extract 操作以： • 將已完成的問卷回應轉換為結構化 FHIR 資源 • 支援 Observation 提取（計分、測量） • 支援資源 Bundle 提取（複雜資料模型） • 自動計算衍生欄位（如得分）調用例： POST /QuestionnaireResponse/qr123/$extract 返回值： { "resourceType": "Bundle", "type": "transaction", "entry": [ { "resource": { "resourceType": "Observation", "code": { "coding": [{ "code": "depression-score" }] }, "value": { "integer": 15 } } } ] } 這是 SDC 工作流的關鍵步驟

CapabilityStatement: My FHIR Client Capability Statement