FHIR IG analytics| Package | medmij.fhir.nl.stu3.core |
| Resource Type | CapabilityStatement |
| Id | CapabilityStatement-medmij-core-FluidBalance-Serve.json |
| FHIR Version | R3 |
| Source | https://simplifier.net/resolve?scope=medmij.fhir.nl.stu3.core@1.0.0&canonical=http://medmij.nl/fhir/CapabilityStatement/medmij-core-FluidBalance-Serve |
| URL | http://medmij.nl/fhir/CapabilityStatement/medmij-core-FluidBalance-Serve |
| Status | active |
| Date | 2026-02-04 |
| Name | MedMij Core FluidBalance Serve |
| Realm | nl |
| Description | This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Fluid balance' transaction within MedMij STU3 Core. |
| Purpose | This CapabilityStatement is informative in nature and does not represent the minimum or maximum set of capabilities the client or server should support. The aim is to design the CapabilityStatement as complete as possible, however for the exact set of capabilities the implementation guide of the corresponding information standard should be consulted. |
| Copyright | Copyright and related rights waived via CC0, https://creativecommons.org/publicdomain/zero/1.0/. This does not apply to information from third parties, for example a medical terminology system. The implementer alone is responsible for identifying and obtaining any necessary licenses or authorizations to utilize third party IP in connection with the specification or otherwise. |
| Kind | requirements |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
{
"resourceType": "CapabilityStatement",
"id": "medmij-core-FluidBalance-Serve",
"url": "http://medmij.nl/fhir/CapabilityStatement/medmij-core-FluidBalance-Serve",
"text": {
"status": "empty",
"div": "<!-- snip (see above) -->"
},
"name": "MedMij Core FluidBalance Serve",
"status": "active",
"date": "2026-02-04",
"publisher": "MedMij",
"contact": [
{
"name": "MedMij",
"telecom": [
{
"system": "email",
"value": "info@medmij.nl",
"use": "work"
}
]
}
],
"description": "This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Fluid balance' transaction within MedMij STU3 Core.",
"purpose": "This CapabilityStatement is informative in nature and does not represent the minimum or maximum set of capabilities the client or server should support. The aim is to design the CapabilityStatement as complete as possible, however for the exact set of capabilities the implementation guide of the corresponding information standard should be consulted.",
"copyright": "Copyright and related rights waived via CC0, https://creativecommons.org/publicdomain/zero/1.0/. This does not apply to information from third parties, for example a medical terminology system. The implementer alone is responsible for identifying and obtaining any necessary licenses or authorizations to utilize third party IP in connection with the specification or otherwise.",
"kind": "requirements",
"fhirVersion": "3.0.2",
"format": [
"xml",
"json"
],
"profile": [
{
"reference": "http://nictiz.nl/fhir/StructureDefinition/zib-FluidBalance",
"display": "zib-FluidBalance"
},
{
"reference": "http://fhir.nl/fhir/StructureDefinition/nl-core-patient",
"display": "nl-core-patient"
},
{
"reference": "http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole",
"display": "nl-core-practitionerrole"
},
{
"reference": "http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner",
"display": "nl-core-practitioner"
},
{
"reference": "http://fhir.nl/fhir/StructureDefinition/nl-core-organization",
"display": "nl-core-organization"
}
],
"rest": [
{
"mode": "server",
"documentation": "Minimal requirements for a server to fulfill the 'Serve Fluid balance' transaction within MedMij STU3 Core (system role: MMC-FBB-zib2017/STU3-1.0.0-beta.1-FHIR).",
"resource": [
{
"type": "Observation",
"interaction": [
{
"code": "search-type"
}
],
"searchParam": [
{
"name": "code",
"type": "token"
}
]
},
{
"type": "Patient",
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
"interaction": [
{
"code": "read",
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"type": "PractitionerRole",
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
"interaction": [
{
"code": "read",
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"type": "Practitioner",
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
"interaction": [
{
"code": "read",
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"type": "Organization",
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
"interaction": [
{
"code": "read",
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
}
],
"interaction": [
{
"code": "search-system"
}
]
}
]
}