Generated Narrative: CapabilityStatement MNCoreServerCapabilityStatement МН Core FHIR Server Capability Statement Implementation Guide Version: 0.1.0 FHIR Version: 4.0.1 Supported Formats: json, xml Published on: 2026-05-10 Published by: Эрүүл мэндийн хөгжлийн төв (Health Development Center, Mongolia) 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 МН Core IG FHIR Сервер Workflow дэмжлэг Workflow A — Нэг удаагийн AMB үзлэг: Patient → Coverage (check) → Encounter (AMB, open) → QuestionnaireResponse (form data) → Observation (vital signs) → Condition (diagnosis, ICD-10) → MedicationRequest (EMM36-1) → ServiceRequest (EMM37-2 lab order) → Encounter (PATCH status=finished) Workflow B — Урт хугацааны асрамж (EpisodeOfCare): Patient → EpisodeOfCare (maternity | chronic | pediatric-growth) → Encounter-1 (Episodic, in-progress) → QuestionnaireResponse → RiskAssessment (per visit — WHO SMART ANC) → Observation (measurements) → CarePlan (updated) → Encounter-1 (PATCH status=finished) → Encounter-2 ... Encounter-N → EpisodeOfCare (PATCH status=finished) Cross-org Lab Workflow (IHE LAB-LTW): Clinic: ServiceRequest (EMM37-2) → Task (requested) Lab: Task (in-progress) → Specimen → Observation[] Lab: DiagnosticReport (final) → Task (completed, output=DiagnosticReport) Clinic: Poll Task.status OR receive Subscription notification Security Enable CORS: yes Security services supported: SMART-on-FHIR OAuth2 / Keycloak. Hospital-scoped tenant filter on all read/write operations. 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 P C D Searches _include _revinclude Operations Patient http://fhir.mn/StructureDefinition/mn-core-patient y y y y y identifier, family, birthdate Coverage http://fhir.mn/StructureDefinition/mn-core-coverage y y y y patient, status Encounter http://fhir.mn/StructureDefinition/mn-core-encounter Additional supported profiles: http://fhir.mn/StructureDefinition/mn-core-encounter-amb http://fhir.mn/StructureDefinition/mn-core-encounter-episodic y y y y y patient, status, date, episode-of-care, service-provider EpisodeOfCare http://fhir.mn/StructureDefinition/mn-core-episode-of-care y y y y y patient, status, type Appointment http://fhir.mn/StructureDefinition/mn-core-appointment y y y y y patient, status, date Observation http://fhir.mn/StructureDefinition/mn-core-observation y y y y patient, code, category, encounter Condition http://fhir.mn/StructureDefinition/mn-core-condition y y y y patient, code, encounter Procedure http://fhir.mn/StructureDefinition/mn-core-procedure y y y y MedicationRequest http://fhir.mn/StructureDefinition/mn-core-medication-request y y y y patient, encounter, status Immunization http://fhir.mn/StructureDefinition/mn-core-immunization y y y y RiskAssessment http://fhir.mn/StructureDefinition/mn-core-risk-assessment y y y y patient, encounter DiagnosticReport http://fhir.mn/StructureDefinition/mn-core-diagnostic-report y y y y patient, based-on, status, category Specimen http://fhir.mn/StructureDefinition/mn-core-specimen y y y y ImagingStudy http://fhir.mn/StructureDefinition/mn-core-imaging-study y y y y ServiceRequest http://fhir.mn/StructureDefinition/mn-core-service-request y y y y patient, status, encounter, performer Task http://fhir.mn/StructureDefinition/mn-core-task y y y y y patient, based-on, status, owner QuestionnaireResponse y y y y patient, encounter, questionnaire, status DocumentReference http://fhir.mn/StructureDefinition/mn-core-document-reference y y y y CarePlan http://fhir.mn/StructureDefinition/mn-core-care-plan y y y y y Consent http://fhir.mn/StructureDefinition/mn-core-consent y y y y ClinicalImpression http://fhir.mn/StructureDefinition/mn-core-clinical-impression y y y y RiskAssessment http://fhir.mn/StructureDefinition/mn-core-risk-assessment y y y y Organization http://fhir.mn/StructureDefinition/mn-core-organization y y y y Practitioner http://fhir.mn/StructureDefinition/mn-core-practitioner y y y y PractitionerRole http://fhir.mn/StructureDefinition/mn-core-practitioner-role y y y y Location http://fhir.mn/StructureDefinition/mn-core-location y y y y HealthcareService y y y y Subscription y y y y Resource Conformance: supported Patient Base System Profile http://fhir.mn/StructureDefinition/mn-core-patient Profile Conformance SHALL Reference Policy Interaction summary Supports read, search-type, create, update, patch. Search Parameters Conformance Parameter Type Documentation SHALL identifier token Register.gov.mn регистрийн дугаараар хайх SHALL family string SHALL birthdate date Resource Conformance: supported Coverage Base System Profile http://fhir.mn/StructureDefinition/mn-core-coverage Profile Conformance SHALL Reference Policy Interaction summary Supports read, search-type, create, update. Search Parameters Conformance Parameter Type Documentation SHALL patient reference SHALL status token Resource Conformance: supported Encounter Base System Profile http://fhir.mn/StructureDefinition/mn-core-encounter Profile Conformance SHALL Reference Policy Supported Profiles http://fhir.mn/StructureDefinition/mn-core-encounter-amb http://fhir.mn/StructureDefinition/mn-core-encounter-episodic Interaction summary Supports read, search-type, create, update, patch. Documentation serviceProvider 1..1 on POST. PATCH exempt (for status updates). Use mn-core-encounter-amb for standalone visits, mn-core-encounter-episodic for EpisodeOfCare-linked visits. Search Parameters Conformance Parameter Type Documentation SHALL patient reference SHALL status token SHALL date date SHALL episode-of-care reference SHALL service-provider reference Resource Conformance: supported EpisodeOfCare Base System Profile http://fhir.mn/StructureDefinition/mn-core-episode-of-care Profile Conformance SHALL Reference Policy Interaction summary Supports read, search-type, create, update, patch. Search Parameters Conformance Parameter Type Documentation SHALL patient reference SHALL status token SHALL type token Resource Conformance: supported Appointment Base System Profile http://fhir.mn/StructureDefinition/mn-core-appointment Profile Conformance SHALL Reference Policy Interaction summary Supports read, search-type, create, update, patch. Search Parameters Conformance Parameter Type Documentation SHALL patient reference SHALL status token SHALL date date Resource Conformance: supported Observation Base System Profile http://fhir.mn/StructureDefinition/mn-core-observation Profile Conformance SHALL Reference Policy Interaction summary Supports read, search-type, create, update. Search Parameters Conformance Parameter Type Documentation SHALL patient reference SHALL code token SHALL category token SHALL encounter reference Resource Conformance: supported Condition Base System Profile http://fhir.mn/StructureDefinition/mn-core-condition Profile Conformance SHALL Reference Policy Interaction summary Supports read, search-type, create, update. Search Parameters Conformance Parameter Type Documentation SHALL patient reference SHALL code token SHALL encounter reference Resource Conformance: supported Procedure Base System Profile http://fhir.mn/StructureDefinition/mn-core-procedure Profile Conformance SHALL Reference Policy Interaction summary Supports read, search-type, create, update. Resource Conformance: supported MedicationRequest Base System Profile http://fhir.mn/StructureDefinition/mn-core-medication-request Profile Conformance SHALL Reference Policy Interaction summary Supports read, search-type, create, update. Search Parameters Conformance Parameter Type Documentation SHALL patient reference SHALL encounter reference SHALL status token Resource Conformance: supported Immunization Base System Profile http://fhir.mn/StructureDefinition/mn-core-immunization Profile Conformance SHALL Reference Policy Interaction summary Supports read, search-type, create, update. Resource Conformance: supported RiskAssessment Base System Profile http://fhir.mn/StructureDefinition/mn-core-risk-assessment Profile Conformance SHALL Reference Policy Interaction summary Supports read, search-type, create, update. Documentation WHO SMART ANC: must be created at every ANC Encounter (mn-core-encounter-episodic within a maternity EpisodeOfCare). Search Parameters Conformance Parameter Type Documentation SHALL patient reference SHALL encounter reference Resource Conformance: supported DiagnosticReport Base System Profile http://fhir.mn/StructureDefinition/mn-core-diagnostic-report Profile Conformance SHALL Reference Policy Interaction summary Supports read, search-type, create, update. Search Parameters Conformance Parameter Type Documentation SHALL patient reference SHALL based-on reference SHALL status token SHALL category token Resource Conformance: supported Specimen Base System Profile http://fhir.mn/StructureDefinition/mn-core-specimen Profile Conformance SHALL Reference Policy Interaction summary Supports read, search-type, create, update. Resource Conformance: supported ImagingStudy Base System Profile http://fhir.mn/StructureDefinition/mn-core-imaging-study Profile Conformance SHALL Reference Policy Interaction summary Supports read, search-type, create, update. Resource Conformance: supported ServiceRequest Base System Profile http://fhir.mn/StructureDefinition/mn-core-service-request Profile Conformance SHALL Reference Policy Interaction summary Supports read, search-type, create, update. Documentation IHE LAB-LTW: Every ServiceRequest for lab/imaging MUST have a corresponding Task (basedOn=ServiceRequest). Lab org creates Task, updates status, links DiagnosticReport in Task.output. Search Parameters Conformance Parameter Type Documentation SHALL patient reference SHALL status token SHALL encounter reference SHALL performer reference Resource Conformance: supported Task Base System Profile http://fhir.mn/StructureDefinition/mn-core-task Profile Conformance SHALL Reference Policy Interaction summary Supports read, search-type, create, update, patch. Documentation IHE LAB-LTW Task lifecycle: requested → received → accepted → in-progress → completed Task.basedOn = Reference(ServiceRequest) [1..1 for lab tasks] Task.input[serviceRequestRef] = Reference(ServiceRequest) Task.output[diagnosticReportRef] = Reference(DiagnosticReport) [populated when completed] Polling pattern (Clinic): GET /Task?based-on=ServiceRequest/{id}&status=completed Search Parameters Conformance Parameter Type Documentation SHALL patient reference SHALL based-on reference SHALL status token SHALL owner reference Resource Conformance: supported QuestionnaireResponse Core FHIR Resource QuestionnaireResponse Reference Policy Interaction summary Supports read, search-type, create, update. Documentation Stored as an immutable legal/audit snapshot of what was submitted. Hospital systems (M2M) send discrete FHIR resources separately; QR is the final complete record. No $extract operation. Search Parameters Conformance Parameter Type Documentation SHALL patient reference SHALL encounter reference SHALL questionnaire reference SHALL status token Resource Conformance: supported DocumentReference Base System Profile http://fhir.mn/StructureDefinition/mn-core-document-reference Profile Conformance SHALL Reference Policy Interaction summary Supports read, search-type, create, update. Documentation IHE MHD ITI-65: clinical documents (certificates, reports). content.attachment.url or base64. Resource Conformance: supported CarePlan Base System Profile http://fhir.mn/StructureDefinition/mn-core-care-plan Profile Conformance SHALL Reference Policy Interaction summary Supports read, search-type, create, update, patch. Resource Conformance: supported Consent Base System Profile http://fhir.mn/StructureDefinition/mn-core-consent Profile Conformance SHALL Reference Policy Interaction summary Supports read, search-type, create, update. Resource Conformance: supported ClinicalImpression Base System Profile http://fhir.mn/StructureDefinition/mn-core-clinical-impression Profile Conformance SHALL Reference Policy Interaction summary Supports read, search-type, create, update. Resource Conformance: supported RiskAssessment Base System Profile http://fhir.mn/StructureDefinition/mn-core-risk-assessment Profile Conformance SHALL Reference Policy Interaction summary Supports read, search-type, create, update. Resource Conformance: supported Organization Base System Profile http://fhir.mn/StructureDefinition/mn-core-organization Profile Conformance SHALL Reference Policy Interaction summary Supports read, search-type, create, update. Resource Conformance: supported Practitioner Base System Profile http://fhir.mn/StructureDefinition/mn-core-practitioner Profile Conformance SHALL Reference Policy Interaction summary Supports read, search-type, create, update. Resource Conformance: supported PractitionerRole Base System Profile http://fhir.mn/StructureDefinition/mn-core-practitioner-role Profile Conformance SHALL Reference Policy Interaction summary Supports read, search-type, create, update. Resource Conformance: supported Location Base System Profile http://fhir.mn/StructureDefinition/mn-core-location Profile Conformance SHALL Reference Policy Interaction summary Supports read, search-type, create, update. Resource Conformance: supported HealthcareService Core FHIR Resource HealthcareService Reference Policy Interaction summary Supports read, search-type, create, update. Resource Conformance: supported Subscription Core FHIR Resource Subscription Reference Policy Interaction summary Supports read, create, update, delete. Documentation Lab PUSH mechanism: Lab organization POSTs a Subscription for DiagnosticReport?category=LAB&status=final targeting the clinic's webhook. Alternative: Clinic polls Task?based-on=ServiceRequest/{id}&status=completed
МН Core FHIR Server Capability Statement
Эрүүл мэндийн хөгжлийн төв (Health Development Center, Mongolia)
Эрүүл мэндийн хөгжлийн төв (Health Development Center)
МН Core IG-ийг дэмждэг FHIR серверийн чадавхийн мэдэгдэл. Лабораторийн cross-org workflow, Subscription, QR $extract дэмждэг.
## МН Core IG FHIR Сервер ### Workflow дэмжлэг **Workflow A — Нэг удаагийн AMB үзлэг:** ``` Patient → Coverage (check) → Encounter (AMB, open) → QuestionnaireResponse (form data) → Observation (vital signs) → Condition (diagnosis, ICD-10) → MedicationRequest (EMM36-1) → ServiceRequest (EMM37-2 lab order) → Encounter (PATCH status=finished) ``` **Workflow B — Урт хугацааны асрамж (EpisodeOfCare):** ``` Patient → EpisodeOfCare (maternity | chronic | pediatric-growth) → Encounter-1 (Episodic, in-progress) → QuestionnaireResponse → RiskAssessment (per visit — WHO SMART ANC) → Observation (measurements) → CarePlan (updated) → Encounter-1 (PATCH status=finished) → Encounter-2 ... Encounter-N → EpisodeOfCare (PATCH status=finished) ``` **Cross-org Lab Workflow (IHE LAB-LTW):** ``` Clinic: ServiceRequest (EMM37-2) → Task (requested) Lab: Task (in-progress) → Specimen → Observation[] Lab: DiagnosticReport (final) → Task (completed, output=DiagnosticReport) Clinic: Poll Task.status OR receive Subscription notification ```
OAuth2 / Keycloak. Hospital-scoped tenant filter on all read/write operations.
Register.gov.mn регистрийн дугаараар хайх
serviceProvider 1..1 on POST. PATCH exempt (for status updates). Use mn-core-encounter-amb for standalone visits, mn-core-encounter-episodic for EpisodeOfCare-linked visits.
WHO SMART ANC: must be created at every ANC Encounter (mn-core-encounter-episodic within a maternity EpisodeOfCare).
IHE LAB-LTW: Every ServiceRequest for lab/imaging MUST have a corresponding Task (basedOn=ServiceRequest). Lab org creates Task, updates status, links DiagnosticReport in Task.output.
IHE LAB-LTW Task lifecycle: requested → received → accepted → in-progress → completed Task.basedOn = Reference(ServiceRequest) [1..1 for lab tasks] Task.input[serviceRequestRef] = Reference(ServiceRequest) Task.output[diagnosticReportRef] = Reference(DiagnosticReport) [populated when completed] Polling pattern (Clinic): GET /Task?based-on=ServiceRequest/{id}&status=completed
Stored as an immutable legal/audit snapshot of what was submitted. Hospital systems (M2M) send discrete FHIR resources separately; QR is the final complete record. No $extract operation.
IHE MHD ITI-65: clinical documents (certificates, reports). content.attachment.url or base64.
Lab PUSH mechanism: Lab organization POSTs a Subscription for DiagnosticReport?category=LAB&status=final targeting the clinic's webhook. Alternative: Clinic polls Task?based-on=ServiceRequest/{id}&status=completed