傳染病通報系統實作指引
0.1.0 - ci-build Taiwan, Province of China flag

傳染病通報系統實作指引, published by 衛福部疾病管制署. 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/fhir-nidrs/nidrs/ and changes regularly. See the Directory of published versions

CapabilityStatement: 傳染病通報系統-伺服端

Official URL: https://cdc.gov.tw/nidrs/CapabilityStatement/CapabilityStatementNidrServer Version: 0.1.0
Active as of 2026-09-01 Computable Name: CapabilityStatementNidrServer

傳染病通報系統-伺服端(Server)之能力聲明

Raw OpenAPI-Swagger Definition file | Download

傳染病通報系統-伺服端

  • Implementation Guide Version: 0.1.0
  • FHIR Version: 4.0.1
  • Supported Formats: application/fhir+json, application/fhir+xml
  • Published on: 2026-09-01
  • Published by: 衛福部疾病管制署

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.

SHALL Support the Following Implementation Guides

FHIR RESTful Capabilities

Mode: server

傳染病通報系統-伺服端必須(SHALL)(1)支援本實作指引中所有profiles (2)根據FHIR規範實作RESTful (3)回傳狀態碼-①(Status 400):無效參數(invalid parameter)、②(Status 401/4xx):未經授權的請求(unauthorized request)、③(Status 403):未充分授權的資料存取範圍(insufficient premission scope)、④(Status 404):未知的resource(unknown resource) (4)支援JSON格式 (5)可識別每個新增到Server的實例(instance)之meta.profile是否為台灣醫院感染管制與抗藥性監測Profiles Defining URL,並確認實例是否依循profile製作。台灣醫院感染管制與抗藥性監測-伺服端建議應該(SHOULD):(1)支援XML格式。

Summary of System-wide Interactions
  • SHOULD support the transactioninteraction.
  • SHOULD support the batchinteraction.

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)

Base System Profile
傳染病通報-Bundle NIDRS
Profile Conformance
SHALL
Reference Policy
resolves

Interaction summary
  • SHALL support create.
  • SHOULD support read, vread, update.
  • SHOULD-NOT support delete.

Profile Conformance
SHALL
Reference Policy
resolves

Interaction summary
  • SHALL support create.
  • SHOULD support read, vread, update.
  • SHOULD-NOT support delete.

Profile Conformance
SHALL
Reference Policy
resolves

Interaction summary
  • SHALL support create.
  • SHOULD support read, vread, update.
  • SHOULD-NOT support delete.

Profile Conformance
SHALL
Reference Policy
resolves

Interaction summary
  • SHALL support create.
  • SHOULD support read, vread, update.
  • SHOULD-NOT support delete.

Profile Conformance
SHALL
Reference Policy
resolves

Interaction summary
  • SHALL support create.
  • SHOULD support read, vread, update.
  • SHOULD-NOT support delete.

Base System Profile
個案資料-Patient NIDRS
Profile Conformance
SHALL
Reference Policy
resolves

Interaction summary
  • SHALL support create.
  • SHOULD support read, vread, update.
  • SHOULD-NOT support delete.

Profile Conformance
SHALL
Reference Policy
resolves

Interaction summary
  • SHALL support create.
  • SHOULD support read, vread, update.
  • SHOULD-NOT support delete.

Profile Conformance
SHALL
Reference Policy
resolves

Interaction summary
  • SHALL support create.
  • SHOULD support read, vread, update.
  • SHOULD-NOT support delete.

Profile Conformance
SHALL
Reference Policy
resolves

Interaction summary
  • SHALL support create.
  • SHOULD support read, vread, update.
  • SHOULD-NOT support delete.

Core FHIR Resource
Observation
Reference Policy
resolves
Interaction summary
  • SHALL support create.
  • SHOULD support read, vread, update.
  • SHOULD-NOT support delete.