このドキュメントは作成中です。

2.5.1. JP Core Server Capability Statement

2.5.1.1. 概要

この章ではJP Core Requestor[クライアント]から発行される問い合わせに対して応答する責務のある、JP Core Serverに要求される機能(expected capabilities)について記載する。
JP Core Serverによってサポートされる FHIR プロファイル・RESTful操作・検索パラメータの完全なリストを定義する。
JP Core Clientは個別のユースケースや意味的な要請に応じてこれらのリストを通じて必要なデータにアクセスすることができる。

項目 内容
定義URL http://jpfhir.jp/fhir/core/CapabilityStatement/StructureDefinition/jp-core-server
バージョン 1.0.0
名前 JPCoreServerCapabilityStatement
タイトル JP Core Server Capability Statement
ステータス アクティブ(2021-12-01)
定義 JP Core Server Actorの期待される機能について説明する。 JP Core ServerがサポートするFHIRプロファイル、OperationsおよびSearch Parametersのリストが定義されている。
公開者 FHIR® Japanese implementation research working group in Japan Association of Medical Informatics (JAMI)
Copyright FHIR® Japanese implementation research working group in Japan Association of Medical Informatics (JAMI)
ソースリソース https://simplifier.net/jp-core-draftv1/jpcoreservercapabilitystatement

2.5.1.2. FHIR RESTful Capabilities

  • JP Coreは以下の要件を必須とする(SHALL)

    • FHIR仕様に基づくRESTfulなふるまいの実装
  • 以下のレスポンスクラスを返すこと

    • (Status 400): invalid parameter
    • (Status 401/4xx): unauthorized request
    • (Status 403): insufficient scope
    • (Status 404): unknown resource
    • (Status 410): deleted resource.
  • 全てのJP Core interactionにおいてjson記述をサポートすること(SHOULD)

  • JP Coreは以下の要件を満たすべきである(SHOULD)

    • 各インスタンス を、FHIR meta.profile 属性の一部としてサポートされる JP Core profileとして認識すること
  • JP Coreでは以下の要件を実装しても良い(MAY)。

    • 全てのJP Core interactionにおいてXML記述をサポートすること
  • セキュリティ

    • See the General Security Considerations section for requirements and recommendations.
    • サーバーはunauthorizedなリクエストに対してはHTTP 401を返さなければならない。(SHALL)

2.5.1.4. 検索条件サマリ

Resource Type Supported Profiles Supported Searches
Patient JP_Patient [SHALL] identifier
[SHOULD] name
[SHOULD] birthdate + name
[SHOULD] birthdate + gender
[SHOULD] birthdate + name + gender
[SHOULD] name + phone
[SHOULD] name + address + postalcode
[MAY] family + given + birthdate + gender + phone + address-postalcode
Coverage JP_Coverage [SHOULD] beneficiary
[SHOULD] class-type
[SHOULD] class-value
[SHOULD] dependent
[SHOULD] identifier
[SHOULD] patient
[SHOULD] payor
[SHOULD] policy-holder
[SHOULD] status
[SHOULD] subscriber
[SHOULD] type
Encounter JP_Encounter [SHALL] patient
[SHALL] date + patient
[SHOULD] identifier
[SHOULD] class + patient
[SHOULD] patient + type
[SHOULD] patient + status
Location JP_Location [SHOULD] name
[SHOULD] address
[SHOULD] address-city
[SHOULD] address-state
[SHOULD] address-postalcode
Organization JP_Organization [SHOULD] identifier
[SHOULD] name
[SHOULD] address
Practitioner JP_Practitioner [SHALL] identifier
[SHALL] name
PractitionerRole JP_PractitionerRole [SHALL] specialty
[SHALL] practitioner
Medication JP_Medication
MedicationRequest JP_MedicationRequest [SHALL] identifier
[SHOULD] patient
[SHOULD] patient + date
[SHOULD] patient + authoredon
[MAY] date + authoredon + category + code + requester
- JP_MedicationRequest_Injection -
MedicationDispense JP_MedicationDispense [SHALL] identifier
[SHOULD] patient
[SHOULD] patient + whenhandedover
[MAY] whenhandedover + whenprepared + context + code + performer
- JP_MedicationDispense_Injection -
MedicationAdministration JP_MedicationAdministration [SHALL] identifier
[SHOULD] patient
[SHOULD] patient + effective-time
[MAY]code
- JP_MedicationAdministration_Injection -
Observation JP_Observation_Common [SHOULD] subject + code + date + based-on
[SHOULD] subject + code + date + value-quantity + based-on
[SHOULD] subject + code + date + value-concept + based-on
[SHOULD] subject + code + date + value-string + based-on
[SHOULD] code + value-quantity + subject
[SHOULD] code + value-concept + subject
[SHOULD] code + value-string + subject
[MAY] patient + category + code + value-quantity
[MAY] patient + category + code + value-quantity + date
[MAY] patient + category + code + value-quantity + encounter
- JP_Observation_LabResult -
- JP_Observation_VitalSigns -
- JP_Observation_BodyMeasurement -
- JP_Observation_PhysicalExam -
- JP_Observation_SocialHistory -
ImagingStudy JP_ImagingStudy_Radiology [SHOULD] subject + modality
[SHOULD] subject + bodysite
[SHOULD] subject + started
[SHOULD] subject + started + modality + bodysite
[SHOULD]encounter
DiagnosticReport JP_DiagnosticReport_Common [SHOULD] subject + category
[SHOULD] subject + category + based-on
[SHOULD] subject + category + date
[MAY]based-on + category + code + conclusion + date + encounter + identifier + issued + media + performer + result + results-interpreter + status + subject
- JP_DiagnosticReport_LabResult -
- JP_DiagnosticReport_Radiology -
AllergyIntolerance JP_AllergyIntolerance [SHALL] patient
[SHALL] patient + date
[SHOULD] patient + clinicalstatus
[SHOULD] patient + verificationstatus
[SHOULD] patient + type
[SHOULD] patient + category
[SHOULD] patient + criticality
Condition JP_Condition [SHALL] patient
[SHALL] patient + date
[SHOULD] patient + clinicalstatus
[SHOULD] patient + verificationstatus
[SHOULD] patient + category
Procedure JP_Procedure [SHALL] patient
[SHALL] patient + date

2.5.1.4. RESTful Capabilities by Resource/Profile:

Capablity StatementリソースはJPCoreServerCapabilityStatementより参照すること。

RESTful Interactions

ModeServer
transactionMAY
batchMAY
search-systemMAY
history-systemMAY

Resource TypeCreateSearchTypeReadVreadUpdatePatchDeleteHistoryInstanceHistoryType
PatientMAYSHALLSHALLSHOULDMAYMAYMAYSHOULDMAY
CoverageMAYSHALLSHALLSHOULDMAYMAYMAYSHOULDMAY
EncounterMAYSHALLSHALLSHOULDMAYMAYMAYSHOULDMAY
LocationMAYSHALLSHALLSHOULDMAYMAYMAYSHOULDMAY
OrganizationMAYSHALLSHALLSHOULDMAYMAYMAYSHOULDMAY
PractitionerMAYSHALLSHALLSHOULDMAYMAYMAYSHOULDMAY
PractitionerRoleMAYSHALLSHALLSHOULDMAYMAYMAYSHOULDMAY
MedicationMAYSHALLSHALLSHOULDMAYMAYMAYSHOULDMAY
MedicationRequestMAYSHALLSHALLSHOULDMAYMAYMAYSHOULDMAY
MedicationDispenseMAYSHALLSHALLSHOULDMAYMAYMAYSHOULDMAY
MedicationAdministrationMAYSHALLSHALLSHOULDMAYMAYMAYSHOULDMAY
ObservationMAYSHALLSHALLSHOULDMAYMAYMAYSHOULDMAY
ImagingStudyMAYSHALLSHALLSHOULDMAYMAYMAYSHOULDMAY
DiagnosticReportMAYSHALLSHALLSHOULDMAYMAYMAYSHOULDMAY
AllergyIntoleranceMAYSHALLSHALLSHOULDMAYMAYMAYSHOULDMAY
ConditionMAYSHALLSHALLSHOULDMAYMAYMAYSHOULDMAY
ProcedureMAYSHALLSHALLSHOULDMAYMAYMAYSHOULDMAY

Search Parameters per resource type

Patient

NameTypeDocumentationLevel
identifiertoken患者IDSHALL
namestring氏名(名前全体)SHOULD
familystringMAY
givenstringMAY
birthdatedate生年月日MAY
gendertoken性別MAY
phonestring電話番号MAY
address-postalcodestring郵便番号MAY

Supported Reverse Includes:

  • Provenance:target

Coverage

NameTypeDocumentationLevel
patientreference患者SHOULD
beneficiaryreference保険受益者SHOULD

Supported Reverse Includes:

  • Provenance:target

Encounter

NameTypeDocumentationLevel
patientreference患者SHALL
identifiertoken外来・入院(外部向け)識別子SHOULD
classtoken分類MAY
datedateイベント発生日MAY
statustoken状態MAY
typetoken具体的な外来・入院の事象MAY

Supported Reverse Includes:

  • Provenance:target

Location

NameTypeDocumentationLevel
namestring場所の名称SHALL
addressstring住所SHALL
address-citystring市区町村SHOULD
address-statestring場所のステータスSHOULD
address-postalcodestring場所の郵便番号SHOULD

Supported Reverse Includes:

  • Provenance:target

Organization

NameTypeDocumentationLevel
identifiertoken組織を識別するための識別子SHOULD
namestring組織名称SHOULD
addressstring組織の住所SHOULD

Supported Reverse Includes:

  • Provenance:target

Practitioner

NameTypeDocumentationLevel
identifiertoken医療従事者の識別子SHALL
namestring医療従事者の名称SHOULD

Supported Reverse Includes:

  • Provenance:target

PractitionerRole

NameTypeDocumentationLevel
specialtytoken医療者の特定の専門性SHALL
practitionerreference医療従事者SHALL

Supported Reverse Includes:

  • Provenance:target

Medication

No search parameters are stated for this resource type

Supported Reverse Includes:

  • Provenance:target

MedicationRequest

NameTypeDocumentationLevel
identifiertoken外部向け識別子SHALL
patientreference患者SHOULD
authoredondate処方発行が最初に行なわれた日MAY
datedate服用開始日MAY
categorytoken薬剤使用区分MAY
codetoken薬品コードMAY
requesterreference処方発行者MAY

Supported Reverse Includes:

  • Provenance:target

MedicationDispense

NameTypeDocumentationLevel
identifiertoken調剤払い出し識別子SHALL
patientreference患者SHOULD
whenhandedoverdate払い出し日時MAY
whenprepareddate調剤日時MAY
codetoken薬品コードMAY
performerreference調剤実施者MAY
encountertoken外来・入院情報MAY

Supported Reverse Includes:

  • Provenance:target

MedicationAdministration

NameTypeDocumentationLevel
identifiertoken薬品識別子(RP番号+薬剤番号)SHALL
patientreference患者SHOULD
effective-timedate実施日時MAY
codetoken薬品コードMAY

Supported Reverse Includes:

  • Provenance:target

Observation

NameTypeLevel
patientreferenceSHOULD
categorytokenMAY
codetokenMAY
datedateMAY
encounterreferenceMAY
value-quantityquantityMAY
value-concepttokenMAY
servicerequestreferenceMAY

Supported Reverse Includes:

  • Provenance:target

ImagingStudy

NameTypeDocumentationLevel
patientreference患者SHOULD
modalitytoken装置MAY
bodysitetoken部位MAY
starteddate検査開始日時MAY
encounterreference外来・入院情報MAY

Supported Reverse Includes:

  • Provenance:target

DiagnosticReport

NameTypeDocumentationLevel
patientreference患者SHOULD
categorytoken臨床分野・部門・診断サービス(CT, US, MRIなど)を分類するコードMAY
codetokenレポートの種別MAY
datedateレポート作成日MAY
servicerequestreferenceオーダー依頼科MAY

Supported Reverse Includes:

  • Provenance:target

AllergyIntolerance

NameTypeDocumentationLevel
patientreference患者SHOULD
clinicalStatustokenアレルギー・不耐性の臨床的なステータスMAY
datedate記載日時MAY
categorytoken特定された原因物質のカテゴリMAY
verificationstatustoken特定された物質に対する反応の傾向や潜在的なリスクの確実性MAY
criticalitytoken特定された物質に対する反応や潜在的な臨床的危害または深刻さの推定MAY

Supported Reverse Includes:

  • Provenance:target

Condition

NameTypeDocumentationLevel
patientreference患者SHOULD
clinicalStatustoken臨床的状態のステータスMAY
datedate記載日時MAY
categorytokenカテゴリMAY
verificationstatustokenclinicalStatusの確からしさMAY

Supported Reverse Includes:

  • Provenance:target

Procedure

NameTypeDocumentationLevel
patientreference患者SHOULD
datedate処置実施日時MAY

Supported Reverse Includes:

  • Provenance:target

Documents

Mode