Generated Narrative: CapabilityStatement MyFHIRServerCapabilityStatement My FHIR Server Capability Statement Implementation Guide Version: 0.2.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 Type Profile R S U C Searches _include _revinclude Operations Patient https://twcore.mohw.gov.tw/ig/twcore/StructureDefinition/Patient-twcore Additional supported profiles: 根據醫院實際病人範例進行資料定義 Y Y _id, birthdate, gender, identifier, name $everything 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 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 QuestionnaireResponse http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaireresponse Additional supported profiles: 評估問卷回覆-總體 Y Y Y Y _id, patient, status, authored, questionnaire $extract Questionnaire http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-extr-obsn Additional supported profiles: 評估問卷 Y Y Y Y identifier, title $populate, $render Resource Conformance: SHOULD Patient Base System Profile TW Core Patient Profile Conformance SHALL Reference Policy Supported Profiles 根據醫院實際病人範例進行資料定義 Interaction summary SHALL 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 Bundle Base System Profile Bundle Profile Conformance SHALL Reference Policy Supported Profiles Bundle-評估資料回傳 Interaction summary SHALL 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 SHALL 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 SHALL 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 SHALL 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 SHALL 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 SHALL 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 SHALL 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 SHALL 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 Practitioner Base System Profile TW Core Practitioner Profile Conformance SHALL Reference Policy Supported Profiles Practitioner Interaction summary SHALL 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 SHALL 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 SHALL 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 QuestionnaireResponse Base System Profile SDC Standard Questionnaire Response Profile Conformance SHALL Reference Policy Supported Profiles 評估問卷回覆-總體 Interaction summary SHALL support read, search-type, create. SHOULD support 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 SHALL $extract The server must implement $extract to: Receive a completed QuestionnaireResponse. Parse extraction extensions from the Questionnaire. Convert the response into structured FHIR resources. Return a Bundle or a single extracted resource. Technical expectations: Support ObservationExtract as the common extraction path. Support DefinitionExtract, TemplateExtract, or StructureMapExtract when required by the Questionnaire design. Extraction priority: Simple Observation extraction, such as scores or measurements. Complex resource extraction, such as diagnosis or medication data. Calculated fields, such as BMI. Transaction Bundle generation. Example response format: { "resourceType": "Bundle", "type": "transaction", "entry": [ { "resource": { "resourceType": "Observation", "code": { "coding": [{ "code": "PHQ9", "system": "http://loinc.org" }] }, "value": { "integer": 12 }, "derivedFrom": [{ "reference": "QuestionnaireResponse/qr123" }] } } ] } This is the final SDC workflow step for importing structured data automatically. Resource Conformance: SHOULD Questionnaire Base System Profile Extractable Questionnaire - Observation Profile Conformance SHALL Reference Policy Supported Profiles 評估問卷 Interaction summary SHALL support read, search-type. SHOULD support create, update. Search Parameters Conformance Parameter Type Documentation SHOULD identifier token SHOULD title string Extended Operations Conformance Operation Documentation SHALL $populate The server must implement $populate to: Receive a pre-population request from a client. Query patient data according to questionnaire.item.definition. Pre-fill answers according to FHIRPath expressions. Return the pre-populated QuestionnaireResponse. Technical expectations: Support a FHIRPath engine. Support data lookup for resources such as Patient and Observation. Parse extensions such as processingPriority, itemWeight, and calculatedExpression. Implementation priority: Basic pre-population from definition. FHIRPath evaluation. answerExpression support. Complex expressions and conditions. Example response format: { "resourceType": "QuestionnaireResponse", "questionnaire": "Questionnaire/q1", "status": "in-progress", "item": [ { "linkId": "patient-name", "answer": [{ "valueString": "[automatically populated patient name]" }] } ] } MAY $render The server may support $render to: Convert Questionnaire into a renderable format, such as HTML, PDF, or JSON. Apply themes or custom presentation rules. Support multilingual rendering. Most clients can render questionnaires themselves, so this operation is optional.
Server CapabilityStatement for the Rehab IG FHIR RESTful API.
The server must implement $extract to: 1. Receive a completed QuestionnaireResponse. 2. Parse extraction extensions from the Questionnaire. 3. Convert the response into structured FHIR resources. 4. Return a Bundle or a single extracted resource. Technical expectations: - Support ObservationExtract as the common extraction path. - Support DefinitionExtract, TemplateExtract, or StructureMapExtract when required by the Questionnaire design. Extraction priority: 1. Simple Observation extraction, such as scores or measurements. 2. Complex resource extraction, such as diagnosis or medication data. 3. Calculated fields, such as BMI. 4. Transaction Bundle generation. Example response format: { "resourceType": "Bundle", "type": "transaction", "entry": [ { "resource": { "resourceType": "Observation", "code": { "coding": [{ "code": "PHQ9", "system": "http://loinc.org" }] }, "value": { "integer": 12 }, "derivedFrom": [{ "reference": "QuestionnaireResponse/qr123" }] } } ] } This is the final SDC workflow step for importing structured data automatically.
The server must implement $populate to: 1. Receive a pre-population request from a client. 2. Query patient data according to questionnaire.item.definition. 3. Pre-fill answers according to FHIRPath expressions. 4. Return the pre-populated QuestionnaireResponse. Technical expectations: - Support a FHIRPath engine. - Support data lookup for resources such as Patient and Observation. - Parse extensions such as processingPriority, itemWeight, and calculatedExpression. Implementation priority: 1. Basic pre-population from definition. 2. FHIRPath evaluation. 3. answerExpression support. 4. Complex expressions and conditions. Example response format: { "resourceType": "QuestionnaireResponse", "questionnaire": "Questionnaire/q1", "status": "in-progress", "item": [ { "linkId": "patient-name", "answer": [{ "valueString": "[automatically populated patient name]" }] } ] }
The server may support $render to: - Convert Questionnaire into a renderable format, such as HTML, PDF, or JSON. - Apply themes or custom presentation rules. - Support multilingual rendering. Most clients can render questionnaires themselves, so this operation is optional.