Generated Narrative: CapabilityStatement MyFHIRClientCapabilityStatement My FHIR Client Capability Statement Implementation Guide Version: 0.2.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 Client REST capabilities and supported search parameters. 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 _include _revinclude Operations Bundle http://hl7.org/fhir/StructureDefinition/Bundle Additional supported profiles: Bundle-評估資料回傳 Y Y _id, identifier CarePlan https://twcore.mohw.gov.tw/ig/twcore/StructureDefinition/CarePlan-twcore Additional supported profiles: Care Plan Y Y patient, category, date, status Condition https://twcore.mohw.gov.tw/ig/twcore/StructureDefinition/Condition-twcore Additional supported profiles: 復健病情、問題、診斷 Y Y _id, clinical-status, code, subject, onset-date, abatement-date, severity Encounter https://twcore.mohw.gov.tw/ig/twcore/StructureDefinition/Encounter-twcore Additional supported profiles: Encounter Y Y _id, class, date, identifier, location, subject, status Goal https://twcore.mohw.gov.tw/ig/twcore/StructureDefinition/Goal-twcore Additional supported profiles: 病人照護計畫的範例 Y Y patient, lifecycle-status, target-date, description MedicationAdministration http://hl7.org/fhir/StructureDefinition/MedicationAdministration Additional supported profiles: Medication Administration Y Y code, identifier, medication, patient, status, context, device, effective-time, performer, reason-given, reason-not-given, request, subject Observation https://twcore.mohw.gov.tw/ig/twcore/StructureDefinition/Observation-screening-assessment-twcore Additional supported profiles: Observation Screening Assessment Y Y _id, category, code, date, performer, status, subject, patient, _lastUpdated Organization https://twcore.mohw.gov.tw/ig/twcore/StructureDefinition/Organization-twcore Additional supported profiles: Organization Y Y _id, identifier, name, type Patient https://twcore.mohw.gov.tw/ig/twcore/StructureDefinition/Patient-twcore Additional supported profiles: 根據醫院實際病人範例進行資料定義 Y Y _id, birthdate, gender, identifier, name $everything Practitioner https://twcore.mohw.gov.tw/ig/twcore/StructureDefinition/Practitioner-twcore Additional supported profiles: Practitioner Y Y _id, identifier, name PractitionerRole https://twcore.mohw.gov.tw/ig/twcore/StructureDefinition/PractitionerRole-twcore Additional supported profiles: PractitionerRole Y Y _id, identifier, specialty Procedure https://twcore.mohw.gov.tw/ig/twcore/StructureDefinition/Procedure-twcore Additional supported profiles: PACProcedure Y Y _id, code, status, subject, date Questionnaire http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-extr-obsn Additional supported profiles: 評估問卷 Y Y identifier, title QuestionnaireResponse http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaireresponse Additional supported profiles: 評估問卷回覆-總體 Y Y Y Y _id, patient, status, authored, questionnaire $extract Resource Conformance: SHOULD Bundle Base System Profile Bundle Profile Conformance SHALL Reference Policy Supported Profiles Bundle-評估資料回傳 Interaction summary SHOULD support read, search-type. Search Parameters Conformance Parameter Type Documentation SHOULD _id token SHOULD identifier token Resource Conformance: SHOULD CarePlan Base System Profile TW Core CarePlan Profile Conformance SHALL Reference Policy Supported Profiles Care Plan Interaction summary SHOULD support read, search-type. Search Parameters Conformance Parameter Type Documentation SHOULD patient reference SHOULD category token SHOULD date date SHOULD status token Resource Conformance: SHOULD Condition Base System Profile TW Core Condition Profile Conformance SHALL Reference Policy Supported Profiles 復健病情、問題、診斷 Interaction summary SHOULD support read, search-type. Search Parameters Conformance Parameter Type Documentation 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: SHOULD Encounter Base System Profile TW Core Encounter Profile Conformance SHALL Reference Policy Supported Profiles Encounter Interaction summary SHOULD support read, search-type. Search Parameters Conformance Parameter Type Documentation SHOULD _id token SHOULD class token SHOULD date date SHOULD identifier token SHOULD location reference SHOULD subject reference SHOULD status token Resource Conformance: SHOULD Goal Base System Profile TW Core Goal Profile Conformance SHALL Reference Policy Supported Profiles 病人照護計畫的範例 Interaction summary SHOULD support read, search-type. Search Parameters Conformance Parameter Type Documentation SHOULD patient reference SHOULD lifecycle-status token SHOULD target-date date SHOULD description token Resource Conformance: SHOULD MedicationAdministration Base System Profile MedicationAdministration Profile Conformance SHALL Reference Policy Supported Profiles Medication Administration Interaction summary SHOULD support read, search-type. Search Parameters Conformance Parameter Type Documentation 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: SHOULD Observation Base System Profile TW Core Observation Screening Assessment Profile Conformance SHALL Reference Policy Supported Profiles Observation Screening Assessment Interaction summary SHOULD support read, search-type. Search Parameters Conformance Parameter Type Documentation 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: SHOULD Organization Base System Profile TW Core Organization Profile Conformance SHALL Reference Policy Supported Profiles Organization Interaction summary SHOULD support read, search-type. Search Parameters Conformance Parameter Type Documentation SHOULD _id token SHOULD identifier token SHOULD name string SHOULD type token Resource Conformance: SHOULD Patient Base System Profile TW Core Patient Profile Conformance SHALL Reference Policy Supported Profiles 根據醫院實際病人範例進行資料定義 Interaction summary SHOULD support read, search-type. Search Parameters Conformance Parameter Type Documentation SHOULD _id token SHOULD birthdate date SHOULD gender token SHOULD identifier token SHOULD name string Extended Operations Conformance Operation Documentation SHOULD $everything Resource Conformance: SHOULD Practitioner Base System Profile TW Core Practitioner Profile Conformance SHALL Reference Policy Supported Profiles Practitioner Interaction summary SHOULD support read, search-type. Search Parameters Conformance Parameter Type Documentation SHOULD _id token SHOULD identifier token SHOULD name string Resource Conformance: SHOULD PractitionerRole Base System Profile TW Core PractitionerRole Profile Conformance SHALL Reference Policy Supported Profiles PractitionerRole Interaction summary SHOULD support read, search-type. Search Parameters Conformance Parameter Type Documentation SHOULD _id token SHOULD identifier token SHOULD specialty token Resource Conformance: SHOULD Procedure Base System Profile TW Core Procedure Profile Conformance SHALL Reference Policy Supported Profiles PACProcedure Interaction summary SHOULD support read, search-type. Search Parameters Conformance Parameter Type Documentation SHOULD _id token SHOULD code token SHOULD status token SHOULD subject reference SHOULD date date Resource Conformance: SHOULD Questionnaire Base System Profile Extractable Questionnaire - Observation Profile Conformance SHALL Reference Policy Supported Profiles 評估問卷 Interaction summary SHOULD support read, search-type. Search Parameters Conformance Parameter Type Documentation SHOULD identifier token SHOULD title string Resource Conformance: SHOULD QuestionnaireResponse Base System Profile SDC Standard Questionnaire Response Profile Conformance SHALL Reference Policy Supported Profiles 評估問卷回覆-總體 Interaction summary SHOULD support read, search-type, create, update. Search Parameters Conformance Parameter Type Documentation SHOULD _id token SHOULD patient reference SHOULD status token SHOULD authored date SHOULD questionnaire reference Extended Operations Conformance Operation Documentation SHOULD $extract Client should be able to call $extract to convert a completed QuestionnaireResponse into structured FHIR resources. Expected workflow: Submit the completed QuestionnaireResponse. Let the server apply the extraction extensions defined on the Questionnaire. Receive Observation or other structured resources. Receive a transaction Bundle when the extracted resources need to be saved together. Example response format: { "resourceType": "Bundle", "type": "transaction", "entry": [ { "resource": { "resourceType": "Observation", "code": { "coding": [{ "code": "depression-score" }] }, "value": { "integer": 15 } } } ] } The actual extraction behavior is determined by SDC and the server implementation.
Client CapabilityStatement for the Rehab IG FHIR RESTful API.
Client REST capabilities and supported search parameters.
Client should be able to call $extract to convert a completed QuestionnaireResponse into structured FHIR resources. Expected workflow: 1. Submit the completed QuestionnaireResponse. 2. Let the server apply the extraction extensions defined on the Questionnaire. 3. Receive Observation or other structured resources. 4. Receive a transaction Bundle when the extracted resources need to be saved together. Example response format: { "resourceType": "Bundle", "type": "transaction", "entry": [ { "resource": { "resourceType": "Observation", "code": { "coding": [{ "code": "depression-score" }] }, "value": { "integer": 15 } } } ] } The actual extraction behavior is determined by SDC and the server implementation.