機器手訓練實作指引 (RoboHand Training Implementation Guide)
0.1.0 - ci-build

機器手訓練實作指引 (RoboHand Training 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 Server Capability Statement

Official URL: http://example.org/fhir/CapabilityStatement/MyFHIRServer Version: 0.1.0
Active as of 2025-10-24 Computable Name: MyFHIRServerCapabilityStatement

此 CapabilityStatement 定義了伺服端必須支援的 FHIR RESTful API 功能

Raw OpenAPI-Swagger Definition file | Download

My FHIR Server Capability Statement

  • Implementation Guide Version: 0.1.0
  • FHIR Version: 4.0.1
  • Supported Formats: xml, json
  • Supported Patch Formats: application/json-patch+json
  • Published on: 2025-10-24
  • 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: server

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 TypeProfileRSUCSearches_include_revincludeOperations
Patienthttp://hl7.org/fhir/StructureDefinition/PatientYY_id, birthdate, gender, identifier, name$everything
Bundlehttp://hl7.org/fhir/StructureDefinition/BundleYY_id, identifier
CarePlanhttp://hl7.org/fhir/StructureDefinition/CarePlanYYpatient, category, date, status
Conditionhttp://hl7.org/fhir/StructureDefinition/ConditionYY_id, clinical-status, code, subject, onset-date, abatement-date, severity
Encounterhttp://hl7.org/fhir/StructureDefinition/EncounterYY_id, class, date, identifier, location, subject, status
Goalhttp://hl7.org/fhir/StructureDefinition/GoalYYpatient, lifecycle-status, target-date, description
MedicationAdministrationhttp://hl7.org/fhir/StructureDefinition/MedicationAdministrationYYcode, identifier, medication, patient, status, context, device, effective-time, performer, reason-given, reason-not-given, request, subject
Observationhttp://hl7.org/fhir/StructureDefinition/ObservationYY_id, category, code, date, performer, status, subject, patient, _lastUpdated
Organizationhttp://hl7.org/fhir/StructureDefinition/OrganizationYY_id, identifier, name, type
Practitionerhttp://hl7.org/fhir/StructureDefinition/PractitionerYY_id, identifier, name
PractitionerRolehttp://hl7.org/fhir/StructureDefinition/PractitionerRoleYY_id, identifier, specialty
Procedurehttp://hl7.org/fhir/StructureDefinition/ProcedureYY_id, code, status, subject, date
QuestionnaireResponsehttp://hl7.org/fhir/StructureDefinition/QuestionnaireResponseYYYY_id, patient, status, authored, questionnaire, subject$extract
Questionnairehttp://hl7.org/fhir/StructureDefinition/QuestionnaireYYYYidentifier, title$populate, $render

Resource Conformance: SHALL Patient

Base System Profile
Patient
Profile Conformance
SHOULD
Reference Policy

Interaction summary
  • SHALL support read, search-type.

Search Parameters
ConformanceParameterTypeDocumentation
SHOULD_idtoken
SHOULDbirthdatedate
SHOULDgendertoken
SHOULDidentifiertoken
SHOULDnamestring
 
Extended Operations
ConformanceOperationDocumentation
SHOULD$everything

Resource Conformance: SHALL Bundle

Base System Profile
Bundle
Profile Conformance
SHOULD
Reference Policy

Interaction summary
  • SHALL support read, search-type.

Search Parameters
ConformanceParameterTypeDocumentation
SHOULD_idtoken
SHOULDidentifiertoken
 

Resource Conformance: SHALL CarePlan

Base System Profile
CarePlan
Profile Conformance
SHOULD
Reference Policy

Interaction summary
  • SHALL support read, search-type.

Search Parameters
ConformanceParameterTypeDocumentation
SHOULDpatientreference
SHOULDcategorytoken
SHOULDdatedate
SHOULDstatustoken
 

Resource Conformance: SHALL Condition

Base System Profile
Condition
Profile Conformance
SHOULD
Reference Policy

Interaction summary
  • SHALL support read, search-type.

Search Parameters
ConformanceParameterTypeDocumentation
SHOULD_idtoken
SHOULDclinical-statustoken
SHOULDcodetoken
SHOULDsubjectreference
SHOULDonset-datedate
SHOULDabatement-datedate
SHOULDseveritytoken
 

Resource Conformance: SHALL Encounter

Base System Profile
Encounter
Profile Conformance
SHOULD
Reference Policy

Interaction summary
  • SHALL support read, search-type.

Search Parameters
ConformanceParameterTypeDocumentation
SHOULD_idtoken
SHOULDclasstoken
SHOULDdatedate
SHOULDidentifiertoken
SHOULDlocationreference
SHOULDsubjectreference
SHOULDstatustoken
 

Resource Conformance: SHALL Goal

Base System Profile
Goal
Profile Conformance
SHOULD
Reference Policy

Interaction summary
  • SHALL support read, search-type.

Search Parameters
ConformanceParameterTypeDocumentation
SHOULDpatientreference
SHOULDlifecycle-statustoken
SHOULDtarget-datedate
SHOULDdescriptiontoken
 

Resource Conformance: SHALL MedicationAdministration

Base System Profile
MedicationAdministration
Profile Conformance
SHOULD
Reference Policy

Interaction summary
  • SHALL support read, search-type.

Search Parameters
ConformanceParameterTypeDocumentation
SHOULDcodetoken
SHOULDidentifiertoken
SHOULDmedicationreference
SHOULDpatientreference
SHOULDstatustoken
SHOULDcontextreference
SHOULDdevicereference
SHOULDeffective-timedate
SHOULDperformerreference
SHOULDreason-giventoken
SHOULDreason-not-giventoken
SHOULDrequestreference
SHOULDsubjectreference
 

Resource Conformance: SHALL Observation

Base System Profile
Observation
Profile Conformance
SHOULD
Reference Policy

Interaction summary
  • SHALL support read, search-type.

Search Parameters
ConformanceParameterTypeDocumentation
SHOULD_idtoken
SHOULDcategorytoken
SHOULDcodetoken
SHOULDdatedate
SHOULDperformerreference
SHOULDstatustoken
SHOULDsubjectreference
SHOULDpatientreference
SHOULD_lastUpdateddate
 

Resource Conformance: SHALL Organization

Base System Profile
Organization
Profile Conformance
SHOULD
Reference Policy

Interaction summary
  • SHALL support read, search-type.

Search Parameters
ConformanceParameterTypeDocumentation
SHOULD_idtoken
SHOULDidentifiertoken
SHOULDnamestring
SHOULDtypetoken
 

Resource Conformance: SHALL Practitioner

Base System Profile
Practitioner
Profile Conformance
SHOULD
Reference Policy

Interaction summary
  • SHALL support read, search-type.

Search Parameters
ConformanceParameterTypeDocumentation
SHOULD_idtoken
SHOULDidentifiertoken
SHOULDnamestring
 

Resource Conformance: SHALL PractitionerRole

Base System Profile
PractitionerRole
Profile Conformance
SHOULD
Reference Policy

Interaction summary
  • SHALL support read, search-type.

Search Parameters
ConformanceParameterTypeDocumentation
SHOULD_idtoken
SHOULDidentifiertoken
SHOULDspecialtytoken
 

Resource Conformance: SHALL Procedure

Base System Profile
Procedure
Profile Conformance
SHOULD
Reference Policy

Interaction summary
  • SHALL support read, search-type.

Search Parameters
ConformanceParameterTypeDocumentation
SHOULD_idtoken
SHOULDcodetoken
SHOULDstatustoken
SHOULDsubjectreference
SHOULDdatedate
 

Resource Conformance: SHALL QuestionnaireResponse

Base System Profile
QuestionnaireResponse
Profile Conformance
SHOULD
Reference Policy

Interaction summary
  • SHALL support read, search-type, create.
  • SHOULD support update.

Search Parameters
ConformanceParameterTypeDocumentation
SHOULD_idtoken
SHOULDpatientreference
SHOULDstatustoken
SHOULDauthoreddate
SHOULDquestionnairereference
SHOULDsubjectreference
 
Extended Operations
ConformanceOperationDocumentation
SHALL$extract

伺服器必須實現 $extract 操作以:

  1. 接收已填寫的 QuestionnaireResponse
  2. 解析 Questionnaire 中的 extraction extension
  3. 根據提取定義轉換為結構化 FHIR 資源
  4. 返回 Bundle 或單一資源

技術要求: • 支援 ObservationExtract(最常見) • 支援 DefinitionExtract(複雜資源) • 支援 TemplateExtract(預設樣板) • StructureMapExtract(高級轉換)

提取優先級:

  1. 簡單 Observation 提取(計分、測量)
  2. 複雜資源提取(診斷/藥物)
  3. 自動計算欄位(如 BMI)
  4. 交易 Bundle 生成

回傳格式: { "resourceType": "Bundle", "type": "transaction", "entry": [ { "resource": { "resourceType": "Observation", "code": { "coding": [{ "code": "PHQ9", "system": "http://loinc.org" }] }, "value": { "integer": 12 }, "derivedFrom": [{ "reference": "QuestionnaireResponse/qr123" }] } } ] }

這是 SDC 工作流的最終步驟,用於自動導入結構化資料

Resource Conformance: SHALL Questionnaire

Base System Profile
Questionnaire
Profile Conformance
SHOULD
Reference Policy

Interaction summary
  • SHALL support read, search-type.
  • SHOULD support create, update.

Search Parameters
ConformanceParameterTypeDocumentation
SHOULDidentifiertoken
SHOULDtitlestring
 
Extended Operations
ConformanceOperationDocumentation
SHALL$populate

伺服器必須實現 $populate 操作以:

  1. 接收 Client 的預填請求
  2. 根據 questionnaire.item.definition 查詢患者資料
  3. 根據 FHIRPath expression 預填答案
  4. 返回已預填的 QuestionnaireResponse

技術要求: • FHIRPath 引擎支援 • 資料查詢引擎(能查詢 Patient/Observation 等資源) • Extension 解析(processingPriority/itemWeight/calculatedExpression)

實現優先級:

  1. 基本預填(根據 definition 字段)
  2. FHIRPath 評估
  3. answerExpression 支援
  4. 複雜表達式與條件

回傳格式: { "resourceType": "QuestionnaireResponse", "questionnaire": "Questionnaire/q1", "status": "in-progress", "item": [ { "linkId": "patient-name", "answer": [{ "valueString": "[自動填入的病人名稱]" }] } ] }

MAY$render

伺服器可選支援 $render 操作以: • 將 Questionnaire 轉換為可用格式(HTML/PDF/JSON) • 應用主題樣式和客製化呈現 • 支援多語言

大多數 Client 會自行實現渲染,此操作非必要