2.2. Capability Statements
The Capability Statements are informative in nature and do not represent the minimum or maximum set of capabilities the client or server should support. The aim is to design the Capability Statements as complete as possible, however for the exact set of capabilities the complete IG should be consulted.
2.2.1. Alert (Retrieve)
This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Retrieve Alert' transaction within MedMij STU3 Core.
REST Capabilities Client
| Mode | Client |
|---|---|
| Documentation | Minimal requirements for a client to fulfill the 'Retrieve Alert' transaction within MedMij STU3 Core (system role: MMC-ALR-zib2017/STU3-rc.3). |
| Search-system | Supported |
Resource Interactions
| Resource Type | SearchType | Read |
|---|---|---|
| Flag | ✓ | |
| Patient | ✓ | |
| PractitionerRole | ✓ | |
| Practitioner | ✓ | |
| Organization | ✓ |
Profiles Supported
| Name | Canonical URL |
|---|---|
| Zib Alerthttp://nictiz.nl/fhir/StructureDefinition/zib-Alert | |
| nl-core-patienthttp://fhir.nl/fhir/StructureDefinition/nl-core-patient | |
| nl-core-practitionerrolehttp://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole | |
| nl-core-practitionerhttp://fhir.nl/fhir/StructureDefinition/nl-core-practitioner | |
| nl-core-organizationhttp://fhir.nl/fhir/StructureDefinition/nl-core-organization |
--- We have skipped the narrative for better readability of the resource ---
</text>
</telecom>
</contact>
<description value="This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Retrieve Alert' transaction within MedMij STU3 Core." />
<purpose value="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 should be consulted." />
<copyright value="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." />
</profile>
</profile>
</profile>
</profile>
</profile>
<documentation value="Minimal requirements for a client to fulfill the 'Retrieve Alert' transaction within MedMij STU3 Core (system role: MMC-ALR-zib2017/STU3-rc.3)." />
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
</interaction>
</rest>
</CapabilityStatement>
{
--- We have skipped the narrative for better readability of the resource ---
},
{
}
],
"description": "This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Retrieve Alert' 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 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.",
"xml",
"json"
],
{
},
{
},
{
},
{
},
{
}
],
{
"documentation": "Minimal requirements for a client to fulfill the 'Retrieve Alert' transaction within MedMij STU3 Core (system role: MMC-ALR-zib2017/STU3-rc.3).",
{
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
}
],
]
}
]
}
2.2.2. Alert (Serve)
This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Alert' transaction within MedMij STU3 Core.
REST Capabilities Server
| Mode | Server |
|---|---|
| Documentation | Minimal requirements for a server to fulfill the 'Serve Alert' transaction within MedMij STU3 Core (system role: MMC-ALB-zib2017/STU3-rc.3). |
| Search-system | Supported |
Resource Interactions
| Resource Type | SearchType | Read |
|---|---|---|
| Flag | ✓ | |
| Patient | ✓ | |
| PractitionerRole | ✓ | |
| Practitioner | ✓ | |
| Organization | ✓ |
Profiles Supported
| Name | Canonical URL |
|---|---|
| Zib Alerthttp://nictiz.nl/fhir/StructureDefinition/zib-Alert | |
| nl-core-patienthttp://fhir.nl/fhir/StructureDefinition/nl-core-patient | |
| nl-core-practitionerrolehttp://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole | |
| nl-core-practitionerhttp://fhir.nl/fhir/StructureDefinition/nl-core-practitioner | |
| nl-core-organizationhttp://fhir.nl/fhir/StructureDefinition/nl-core-organization |
--- We have skipped the narrative for better readability of the resource ---
</text>
</telecom>
</contact>
<description value="This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Alert' transaction within MedMij STU3 Core." />
<purpose value="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 should be consulted." />
<copyright value="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." />
</profile>
</profile>
</profile>
</profile>
</profile>
<documentation value="Minimal requirements for a server to fulfill the 'Serve Alert' transaction within MedMij STU3 Core (system role: MMC-ALB-zib2017/STU3-rc.3)." />
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
</interaction>
</rest>
</CapabilityStatement>
{
--- We have skipped the narrative for better readability of the resource ---
},
{
}
],
"description": "This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Alert' 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 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.",
"xml",
"json"
],
{
},
{
},
{
},
{
},
{
}
],
{
"documentation": "Minimal requirements for a server to fulfill the 'Serve Alert' transaction within MedMij STU3 Core (system role: MMC-ALB-zib2017/STU3-rc.3).",
{
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
}
],
]
}
]
}
2.2.3. Blood Pressure (Retrieve)
This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Retrieve Blood pressure' transaction within MedMij STU3 Core.
REST Capabilities Client
| Mode | Client |
|---|---|
| Documentation | Minimal requirements for a client to fulfill the 'Retrieve Blood pressure' transaction within MedMij STU3 Core (system role: MMC-BPR-zib2017/STU3-rc.3). |
| Search-system | Supported |
Resource Interactions
| Resource Type | SearchType | Read |
|---|---|---|
| Observation | ✓ | |
| Patient | ✓ | |
| PractitionerRole | ✓ | |
| Practitioner | ✓ | |
| Organization | ✓ |
Search Parameters per resource type
Observation
| Name | Type | Level |
|---|---|---|
| code | token | Supported |
Patient
No search parameters are stated for this resource type
PractitionerRole
No search parameters are stated for this resource type
Practitioner
No search parameters are stated for this resource type
Organization
No search parameters are stated for this resource type
Profiles Supported
| Name | Canonical URL |
|---|---|
| Zib BloodPressurehttp://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure | |
| nl-core-patienthttp://fhir.nl/fhir/StructureDefinition/nl-core-patient | |
| nl-core-practitionerrolehttp://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole | |
| nl-core-practitionerhttp://fhir.nl/fhir/StructureDefinition/nl-core-practitioner | |
| nl-core-organizationhttp://fhir.nl/fhir/StructureDefinition/nl-core-organization |
--- We have skipped the narrative for better readability of the resource ---
</text>
</telecom>
</contact>
<description value="This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Retrieve Blood pressure' transaction within MedMij STU3 Core." />
<purpose value="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 should be consulted." />
<copyright value="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." />
</profile>
</profile>
</profile>
</profile>
</profile>
<documentation value="Minimal requirements for a client to fulfill the 'Retrieve Blood pressure' transaction within MedMij STU3 Core (system role: MMC-BPR-zib2017/STU3-rc.3)." />
</interaction>
</searchParam>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
</interaction>
</rest>
</CapabilityStatement>
{
--- We have skipped the narrative for better readability of the resource ---
},
{
}
],
"description": "This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Retrieve Blood pressure' 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 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.",
"xml",
"json"
],
{
},
{
},
{
},
{
},
{
}
],
{
"documentation": "Minimal requirements for a client to fulfill the 'Retrieve Blood pressure' transaction within MedMij STU3 Core (system role: MMC-BPR-zib2017/STU3-rc.3).",
{
],
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
}
],
]
}
]
}
2.2.4. Blood Pressure (Serve)
This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Blood pressure' transaction within MedMij STU3 Core.
REST Capabilities Server
| Mode | Server |
|---|---|
| Documentation | Minimal requirements for a server to fulfill the 'Serve Blood pressure' transaction within MedMij STU3 Core (system role: MMC-BPB-zib2017/STU3-rc.3). |
| Search-system | Supported |
Resource Interactions
| Resource Type | SearchType | Read |
|---|---|---|
| Observation | ✓ | |
| Patient | ✓ | |
| PractitionerRole | ✓ | |
| Practitioner | ✓ | |
| Organization | ✓ |
Search Parameters per resource type
Observation
| Name | Type | Level |
|---|---|---|
| code | token | Supported |
Patient
No search parameters are stated for this resource type
PractitionerRole
No search parameters are stated for this resource type
Practitioner
No search parameters are stated for this resource type
Organization
No search parameters are stated for this resource type
Profiles Supported
| Name | Canonical URL |
|---|---|
| Zib BloodPressurehttp://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure | |
| nl-core-patienthttp://fhir.nl/fhir/StructureDefinition/nl-core-patient | |
| nl-core-practitionerrolehttp://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole | |
| nl-core-practitionerhttp://fhir.nl/fhir/StructureDefinition/nl-core-practitioner | |
| nl-core-organizationhttp://fhir.nl/fhir/StructureDefinition/nl-core-organization |
--- We have skipped the narrative for better readability of the resource ---
</text>
</telecom>
</contact>
<description value="This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Blood pressure' transaction within MedMij STU3 Core." />
<purpose value="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 should be consulted." />
<copyright value="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." />
</profile>
</profile>
</profile>
</profile>
</profile>
<documentation value="Minimal requirements for a server to fulfill the 'Serve Blood pressure' transaction within MedMij STU3 Core (system role: MMC-BPB-zib2017/STU3-rc.3)." />
</interaction>
</searchParam>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
</interaction>
</rest>
</CapabilityStatement>
{
--- We have skipped the narrative for better readability of the resource ---
},
{
}
],
"description": "This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Blood pressure' 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 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.",
"xml",
"json"
],
{
},
{
},
{
},
{
},
{
}
],
{
"documentation": "Minimal requirements for a server to fulfill the 'Serve Blood pressure' transaction within MedMij STU3 Core (system role: MMC-BPB-zib2017/STU3-rc.3).",
{
],
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
}
],
]
}
]
}
2.2.5. Body Height (Retrieve)
This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Retrieve Body height' transaction within MedMij STU3 Core.
REST Capabilities Client
| Mode | Client |
|---|---|
| Documentation | Minimal requirements for a client to fulfill the 'Retrieve Body height' transaction within MedMij STU3 Core (system role: MMC-BHR-zib2017/STU3-rc.3). |
| Search-system | Supported |
Resource Interactions
| Resource Type | SearchType | Read |
|---|---|---|
| Observation | ✓ | |
| Patient | ✓ | |
| PractitionerRole | ✓ | |
| Practitioner | ✓ | |
| Organization | ✓ |
Search Parameters per resource type
Observation
| Name | Type | Level |
|---|---|---|
| code | token | Supported |
Patient
No search parameters are stated for this resource type
PractitionerRole
No search parameters are stated for this resource type
Practitioner
No search parameters are stated for this resource type
Organization
No search parameters are stated for this resource type
Profiles Supported
| Name | Canonical URL |
|---|---|
| Zib BodyHeighthttp://nictiz.nl/fhir/StructureDefinition/zib-BodyHeight | |
| nl-core-patienthttp://fhir.nl/fhir/StructureDefinition/nl-core-patient | |
| nl-core-practitionerrolehttp://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole | |
| nl-core-practitionerhttp://fhir.nl/fhir/StructureDefinition/nl-core-practitioner | |
| nl-core-organizationhttp://fhir.nl/fhir/StructureDefinition/nl-core-organization |
--- We have skipped the narrative for better readability of the resource ---
</text>
</telecom>
</contact>
<description value="This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Retrieve Body height' transaction within MedMij STU3 Core." />
<purpose value="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 should be consulted." />
<copyright value="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." />
</profile>
</profile>
</profile>
</profile>
</profile>
<documentation value="Minimal requirements for a client to fulfill the 'Retrieve Body height' transaction within MedMij STU3 Core (system role: MMC-BHR-zib2017/STU3-rc.3)." />
</interaction>
</searchParam>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
</interaction>
</rest>
</CapabilityStatement>
{
--- We have skipped the narrative for better readability of the resource ---
},
{
}
],
"description": "This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Retrieve Body height' 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 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.",
"xml",
"json"
],
{
},
{
},
{
},
{
},
{
}
],
{
"documentation": "Minimal requirements for a client to fulfill the 'Retrieve Body height' transaction within MedMij STU3 Core (system role: MMC-BHR-zib2017/STU3-rc.3).",
{
],
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
}
],
]
}
]
}
2.2.6. Body Height (Serve)
This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Body height' transaction within MedMij STU3 Core.
REST Capabilities Server
| Mode | Server |
|---|---|
| Documentation | Minimal requirements for a server to fulfill the 'Serve Body height' transaction within MedMij STU3 Core (system role: MMC-BHB-zib2017/STU3-rc.3). |
| Search-system | Supported |
Resource Interactions
| Resource Type | SearchType | Read |
|---|---|---|
| Observation | ✓ | |
| Patient | ✓ | |
| PractitionerRole | ✓ | |
| Practitioner | ✓ | |
| Organization | ✓ |
Search Parameters per resource type
Observation
| Name | Type | Level |
|---|---|---|
| code | token | Supported |
Patient
No search parameters are stated for this resource type
PractitionerRole
No search parameters are stated for this resource type
Practitioner
No search parameters are stated for this resource type
Organization
No search parameters are stated for this resource type
Profiles Supported
| Name | Canonical URL |
|---|---|
| Zib BodyHeighthttp://nictiz.nl/fhir/StructureDefinition/zib-BodyHeight | |
| nl-core-patienthttp://fhir.nl/fhir/StructureDefinition/nl-core-patient | |
| nl-core-practitionerrolehttp://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole | |
| nl-core-practitionerhttp://fhir.nl/fhir/StructureDefinition/nl-core-practitioner | |
| nl-core-organizationhttp://fhir.nl/fhir/StructureDefinition/nl-core-organization |
--- We have skipped the narrative for better readability of the resource ---
</text>
</telecom>
</contact>
<description value="This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Body height' transaction within MedMij STU3 Core." />
<purpose value="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 should be consulted." />
<copyright value="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." />
</profile>
</profile>
</profile>
</profile>
</profile>
<documentation value="Minimal requirements for a server to fulfill the 'Serve Body height' transaction within MedMij STU3 Core (system role: MMC-BHB-zib2017/STU3-rc.3)." />
</interaction>
</searchParam>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
</interaction>
</rest>
</CapabilityStatement>
{
--- We have skipped the narrative for better readability of the resource ---
},
{
}
],
"description": "This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Body height' 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 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.",
"xml",
"json"
],
{
},
{
},
{
},
{
},
{
}
],
{
"documentation": "Minimal requirements for a server to fulfill the 'Serve Body height' transaction within MedMij STU3 Core (system role: MMC-BHB-zib2017/STU3-rc.3).",
{
],
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
}
],
]
}
]
}
2.2.7. Body Temperature (Retrieve)
This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Retrieve Body temperature' transaction within MedMij STU3 Core.
REST Capabilities Client
| Mode | Client |
|---|---|
| Documentation | Minimal requirements for a client to fulfill the 'Retrieve Body temperature' transaction within MedMij STU3 Core (system role: MMC-BTR-zib2017/STU3-rc.3). |
| Search-system | Supported |
Resource Interactions
| Resource Type | SearchType | Read |
|---|---|---|
| Observation | ✓ | |
| Patient | ✓ | |
| PractitionerRole | ✓ | |
| Practitioner | ✓ | |
| Organization | ✓ |
Search Parameters per resource type
Observation
| Name | Type | Level |
|---|---|---|
| code | token | Supported |
Patient
No search parameters are stated for this resource type
PractitionerRole
No search parameters are stated for this resource type
Practitioner
No search parameters are stated for this resource type
Organization
No search parameters are stated for this resource type
Profiles Supported
| Name | Canonical URL |
|---|---|
| Zib BodyTemperaturehttp://nictiz.nl/fhir/StructureDefinition/zib-BodyTemperature | |
| nl-core-patienthttp://fhir.nl/fhir/StructureDefinition/nl-core-patient | |
| nl-core-practitionerrolehttp://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole | |
| nl-core-practitionerhttp://fhir.nl/fhir/StructureDefinition/nl-core-practitioner | |
| nl-core-organizationhttp://fhir.nl/fhir/StructureDefinition/nl-core-organization |
--- We have skipped the narrative for better readability of the resource ---
</text>
</telecom>
</contact>
<description value="This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Retrieve Body temperature' transaction within MedMij STU3 Core." />
<purpose value="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 should be consulted." />
<copyright value="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." />
</profile>
</profile>
</profile>
</profile>
</profile>
<documentation value="Minimal requirements for a client to fulfill the 'Retrieve Body temperature' transaction within MedMij STU3 Core (system role: MMC-BTR-zib2017/STU3-rc.3)." />
</interaction>
</searchParam>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
</interaction>
</rest>
</CapabilityStatement>
{
--- We have skipped the narrative for better readability of the resource ---
},
{
}
],
"description": "This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Retrieve Body temperature' 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 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.",
"xml",
"json"
],
{
},
{
},
{
},
{
},
{
}
],
{
"documentation": "Minimal requirements for a client to fulfill the 'Retrieve Body temperature' transaction within MedMij STU3 Core (system role: MMC-BTR-zib2017/STU3-rc.3).",
{
],
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
}
],
]
}
]
}
2.2.8. Body Temperature (Serve)
This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Body temperature' transaction within MedMij STU3 Core.
REST Capabilities Server
| Mode | Server |
|---|---|
| Documentation | Minimal requirements for a server to fulfill the 'Serve Body temperature' transaction within MedMij STU3 Core (system role: MMC-BTB-zib2017/STU3-rc.3). |
| Search-system | Supported |
Resource Interactions
| Resource Type | SearchType | Read |
|---|---|---|
| Observation | ✓ | |
| Patient | ✓ | |
| PractitionerRole | ✓ | |
| Practitioner | ✓ | |
| Organization | ✓ |
Search Parameters per resource type
Observation
| Name | Type | Level |
|---|---|---|
| code | token | Supported |
Patient
No search parameters are stated for this resource type
PractitionerRole
No search parameters are stated for this resource type
Practitioner
No search parameters are stated for this resource type
Organization
No search parameters are stated for this resource type
Profiles Supported
| Name | Canonical URL |
|---|---|
| Zib BodyTemperaturehttp://nictiz.nl/fhir/StructureDefinition/zib-BodyTemperature | |
| nl-core-patienthttp://fhir.nl/fhir/StructureDefinition/nl-core-patient | |
| nl-core-practitionerrolehttp://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole | |
| nl-core-practitionerhttp://fhir.nl/fhir/StructureDefinition/nl-core-practitioner | |
| nl-core-organizationhttp://fhir.nl/fhir/StructureDefinition/nl-core-organization |
--- We have skipped the narrative for better readability of the resource ---
</text>
</telecom>
</contact>
<description value="This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Body temperature' transaction within MedMij STU3 Core." />
<purpose value="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 should be consulted." />
<copyright value="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." />
</profile>
</profile>
</profile>
</profile>
</profile>
<documentation value="Minimal requirements for a server to fulfill the 'Serve Body temperature' transaction within MedMij STU3 Core (system role: MMC-BTB-zib2017/STU3-rc.3)." />
</interaction>
</searchParam>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
</interaction>
</rest>
</CapabilityStatement>
{
--- We have skipped the narrative for better readability of the resource ---
},
{
}
],
"description": "This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Body temperature' 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 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.",
"xml",
"json"
],
{
},
{
},
{
},
{
},
{
}
],
{
"documentation": "Minimal requirements for a server to fulfill the 'Serve Body temperature' transaction within MedMij STU3 Core (system role: MMC-BTB-zib2017/STU3-rc.3).",
{
],
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
}
],
]
}
]
}
2.2.9. Body Weight (Retrieve)
This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Retrieve Body weight' transaction within MedMij STU3 Core.
REST Capabilities Client
| Mode | Client |
|---|---|
| Documentation | Minimal requirements for a client to fulfill the 'Retrieve Body weight' transaction within MedMij STU3 Core (system role: MMC-BWR-zib2017/STU3-rc.3). |
| Search-system | Supported |
Resource Interactions
| Resource Type | SearchType | Read |
|---|---|---|
| Observation | ✓ | |
| Patient | ✓ | |
| PractitionerRole | ✓ | |
| Practitioner | ✓ | |
| Organization | ✓ |
Search Parameters per resource type
Observation
| Name | Type | Level |
|---|---|---|
| code | token | Supported |
Patient
No search parameters are stated for this resource type
PractitionerRole
No search parameters are stated for this resource type
Practitioner
No search parameters are stated for this resource type
Organization
No search parameters are stated for this resource type
Profiles Supported
| Name | Canonical URL |
|---|---|
| Zib BodyWeighthttp://nictiz.nl/fhir/StructureDefinition/zib-BodyWeight | |
| nl-core-patienthttp://fhir.nl/fhir/StructureDefinition/nl-core-patient | |
| nl-core-practitionerrolehttp://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole | |
| nl-core-practitionerhttp://fhir.nl/fhir/StructureDefinition/nl-core-practitioner | |
| nl-core-organizationhttp://fhir.nl/fhir/StructureDefinition/nl-core-organization |
--- We have skipped the narrative for better readability of the resource ---
</text>
</telecom>
</contact>
<description value="This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Retrieve Body weight' transaction within MedMij STU3 Core." />
<purpose value="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 should be consulted." />
<copyright value="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." />
</profile>
</profile>
</profile>
</profile>
</profile>
<documentation value="Minimal requirements for a client to fulfill the 'Retrieve Body weight' transaction within MedMij STU3 Core (system role: MMC-BWR-zib2017/STU3-rc.3)." />
</interaction>
</searchParam>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
</interaction>
</rest>
</CapabilityStatement>
{
--- We have skipped the narrative for better readability of the resource ---
},
{
}
],
"description": "This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Retrieve Body weight' 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 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.",
"xml",
"json"
],
{
},
{
},
{
},
{
},
{
}
],
{
"documentation": "Minimal requirements for a client to fulfill the 'Retrieve Body weight' transaction within MedMij STU3 Core (system role: MMC-BWR-zib2017/STU3-rc.3).",
{
],
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
}
],
]
}
]
}
2.2.10. Body Weight (Serve)
This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Body weight' transaction within MedMij STU3 Core.
REST Capabilities Server
| Mode | Server |
|---|---|
| Documentation | Minimal requirements for a server to fulfill the 'Serve Body weight' transaction within MedMij STU3 Core (system role: MMC-BWB-zib2017/STU3-rc.3). |
| Search-system | Supported |
Resource Interactions
| Resource Type | SearchType | Read |
|---|---|---|
| Observation | ✓ | |
| Patient | ✓ | |
| PractitionerRole | ✓ | |
| Practitioner | ✓ | |
| Organization | ✓ |
Search Parameters per resource type
Observation
| Name | Type | Level |
|---|---|---|
| code | token | Supported |
Patient
No search parameters are stated for this resource type
PractitionerRole
No search parameters are stated for this resource type
Practitioner
No search parameters are stated for this resource type
Organization
No search parameters are stated for this resource type
Profiles Supported
| Name | Canonical URL |
|---|---|
| Zib BodyWeighthttp://nictiz.nl/fhir/StructureDefinition/zib-BodyWeight | |
| nl-core-patienthttp://fhir.nl/fhir/StructureDefinition/nl-core-patient | |
| nl-core-practitionerrolehttp://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole | |
| nl-core-practitionerhttp://fhir.nl/fhir/StructureDefinition/nl-core-practitioner | |
| nl-core-organizationhttp://fhir.nl/fhir/StructureDefinition/nl-core-organization |
--- We have skipped the narrative for better readability of the resource ---
</text>
</telecom>
</contact>
<description value="This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Body weight' transaction within MedMij STU3 Core." />
<purpose value="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 should be consulted." />
<copyright value="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." />
</profile>
</profile>
</profile>
</profile>
</profile>
<documentation value="Minimal requirements for a server to fulfill the 'Serve Body weight' transaction within MedMij STU3 Core (system role: MMC-BWB-zib2017/STU3-rc.3)." />
</interaction>
</searchParam>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
</interaction>
</rest>
</CapabilityStatement>
{
--- We have skipped the narrative for better readability of the resource ---
},
{
}
],
"description": "This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Body weight' 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 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.",
"xml",
"json"
],
{
},
{
},
{
},
{
},
{
}
],
{
"documentation": "Minimal requirements for a server to fulfill the 'Serve Body weight' transaction within MedMij STU3 Core (system role: MMC-BWB-zib2017/STU3-rc.3).",
{
],
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
}
],
]
}
]
}
2.2.11. Fluid Balance (Retrieve)
This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Retrieve Fluid balance' transaction within MedMij STU3 Core.
REST Capabilities Client
| Mode | Client |
|---|---|
| Documentation | Minimal requirements for a client to fulfill the 'Retrieve Fluid balance' transaction within MedMij STU3 Core (system role: MMC-FBR-zib2017/STU3-rc.3). |
| Search-system | Supported |
Resource Interactions
| Resource Type | SearchType | Read |
|---|---|---|
| Observation | ✓ | |
| Patient | ✓ | |
| PractitionerRole | ✓ | |
| Practitioner | ✓ | |
| Organization | ✓ |
Search Parameters per resource type
Observation
| Name | Type | Level |
|---|---|---|
| code | token | Supported |
Patient
No search parameters are stated for this resource type
PractitionerRole
No search parameters are stated for this resource type
Practitioner
No search parameters are stated for this resource type
Organization
No search parameters are stated for this resource type
Profiles Supported
| Name | Canonical URL |
|---|---|
| Zib FluidBalancehttp://nictiz.nl/fhir/StructureDefinition/zib-FluidBalance | |
| nl-core-patienthttp://fhir.nl/fhir/StructureDefinition/nl-core-patient | |
| nl-core-practitionerrolehttp://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole | |
| nl-core-practitionerhttp://fhir.nl/fhir/StructureDefinition/nl-core-practitioner | |
| nl-core-organizationhttp://fhir.nl/fhir/StructureDefinition/nl-core-organization |
--- We have skipped the narrative for better readability of the resource ---
</text>
</telecom>
</contact>
<description value="This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Retrieve Fluid balance' transaction within MedMij STU3 Core." />
<purpose value="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 should be consulted." />
<copyright value="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." />
</profile>
</profile>
</profile>
</profile>
</profile>
<documentation value="Minimal requirements for a client to fulfill the 'Retrieve Fluid balance' transaction within MedMij STU3 Core (system role: MMC-FBR-zib2017/STU3-rc.3)." />
</interaction>
</searchParam>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
</interaction>
</rest>
</CapabilityStatement>
{
--- We have skipped the narrative for better readability of the resource ---
},
{
}
],
"description": "This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Retrieve 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 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.",
"xml",
"json"
],
{
},
{
},
{
},
{
},
{
}
],
{
"documentation": "Minimal requirements for a client to fulfill the 'Retrieve Fluid balance' transaction within MedMij STU3 Core (system role: MMC-FBR-zib2017/STU3-rc.3).",
{
],
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
}
],
]
}
]
}
2.2.12. Fluid Balance (Serve)
This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Fluid balance' transaction within MedMij STU3 Core.
REST Capabilities Server
| 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-rc.3). |
| Search-system | Supported |
Resource Interactions
| Resource Type | SearchType | Read |
|---|---|---|
| Observation | ✓ | |
| Patient | ✓ | |
| PractitionerRole | ✓ | |
| Practitioner | ✓ | |
| Organization | ✓ |
Search Parameters per resource type
Observation
| Name | Type | Level |
|---|---|---|
| code | token | Supported |
Patient
No search parameters are stated for this resource type
PractitionerRole
No search parameters are stated for this resource type
Practitioner
No search parameters are stated for this resource type
Organization
No search parameters are stated for this resource type
Profiles Supported
| Name | Canonical URL |
|---|---|
| Zib FluidBalancehttp://nictiz.nl/fhir/StructureDefinition/zib-FluidBalance | |
| nl-core-patienthttp://fhir.nl/fhir/StructureDefinition/nl-core-patient | |
| nl-core-practitionerrolehttp://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole | |
| nl-core-practitionerhttp://fhir.nl/fhir/StructureDefinition/nl-core-practitioner | |
| nl-core-organizationhttp://fhir.nl/fhir/StructureDefinition/nl-core-organization |
--- We have skipped the narrative for better readability of the resource ---
</text>
</telecom>
</contact>
<description value="This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Fluid balance' transaction within MedMij STU3 Core." />
<purpose value="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 should be consulted." />
<copyright value="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." />
</profile>
</profile>
</profile>
</profile>
</profile>
<documentation value="Minimal requirements for a server to fulfill the 'Serve Fluid balance' transaction within MedMij STU3 Core (system role: MMC-FBB-zib2017/STU3-rc.3)." />
</interaction>
</searchParam>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
</interaction>
</rest>
</CapabilityStatement>
{
--- We have skipped the narrative for better readability of the resource ---
},
{
}
],
"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 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.",
"xml",
"json"
],
{
},
{
},
{
},
{
},
{
}
],
{
"documentation": "Minimal requirements for a server to fulfill the 'Serve Fluid balance' transaction within MedMij STU3 Core (system role: MMC-FBB-zib2017/STU3-rc.3).",
{
],
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
}
],
]
}
]
}
2.2.13. Living Situation (Retrieve)
This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Retrieve Living situation' transaction within MedMij STU3 Core.
REST Capabilities Client
| Mode | Client |
|---|---|
| Documentation | Minimal requirements for a client to fulfill the 'Retrieve Living situation' transaction within MedMij STU3 Core (system role: MMC-LSR-zib2017/STU3-rc.3). |
| Search-system | Supported |
Resource Interactions
| Resource Type | SearchType | Read |
|---|---|---|
| Observation | ✓ | |
| Patient | ✓ | |
| PractitionerRole | ✓ | |
| Practitioner | ✓ | |
| Organization | ✓ |
Search Parameters per resource type
Observation
| Name | Type | Level |
|---|---|---|
| code | token | Supported |
Patient
No search parameters are stated for this resource type
PractitionerRole
No search parameters are stated for this resource type
Practitioner
No search parameters are stated for this resource type
Organization
No search parameters are stated for this resource type
Profiles Supported
| Name | Canonical URL |
|---|---|
| Zib LivingSituationhttp://nictiz.nl/fhir/StructureDefinition/zib-LivingSituation | |
| nl-core-patienthttp://fhir.nl/fhir/StructureDefinition/nl-core-patient | |
| nl-core-practitionerrolehttp://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole | |
| nl-core-practitionerhttp://fhir.nl/fhir/StructureDefinition/nl-core-practitioner | |
| nl-core-organizationhttp://fhir.nl/fhir/StructureDefinition/nl-core-organization |
--- We have skipped the narrative for better readability of the resource ---
</text>
</telecom>
</contact>
<description value="This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Retrieve Living situation' transaction within MedMij STU3 Core." />
<purpose value="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 should be consulted." />
<copyright value="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." />
</profile>
</profile>
</profile>
</profile>
</profile>
<documentation value="Minimal requirements for a client to fulfill the 'Retrieve Living situation' transaction within MedMij STU3 Core (system role: MMC-LSR-zib2017/STU3-rc.3)." />
</interaction>
</searchParam>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
</interaction>
</rest>
</CapabilityStatement>
{
--- We have skipped the narrative for better readability of the resource ---
},
{
}
],
"description": "This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Retrieve Living situation' 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 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.",
"xml",
"json"
],
{
},
{
},
{
},
{
},
{
}
],
{
"documentation": "Minimal requirements for a client to fulfill the 'Retrieve Living situation' transaction within MedMij STU3 Core (system role: MMC-LSR-zib2017/STU3-rc.3).",
{
],
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
}
],
]
}
]
}
2.2.14. Living Situation (Serve)
This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Living situation' transaction within MedMij STU3 Core.
REST Capabilities Server
| Mode | Server |
|---|---|
| Documentation | Minimal requirements for a server to fulfill the 'Serve Living situation' transaction within MedMij STU3 Core (system role: MMC-LSB-zib2017/STU3-rc.3). |
| Search-system | Supported |
Resource Interactions
| Resource Type | SearchType | Read |
|---|---|---|
| Observation | ✓ | |
| Patient | ✓ | |
| PractitionerRole | ✓ | |
| Practitioner | ✓ | |
| Organization | ✓ |
Search Parameters per resource type
Observation
| Name | Type | Level |
|---|---|---|
| code | token | Supported |
Patient
No search parameters are stated for this resource type
PractitionerRole
No search parameters are stated for this resource type
Practitioner
No search parameters are stated for this resource type
Organization
No search parameters are stated for this resource type
Profiles Supported
| Name | Canonical URL |
|---|---|
| Zib LivingSituationhttp://nictiz.nl/fhir/StructureDefinition/zib-LivingSituation | |
| nl-core-patienthttp://fhir.nl/fhir/StructureDefinition/nl-core-patient | |
| nl-core-practitionerrolehttp://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole | |
| nl-core-practitionerhttp://fhir.nl/fhir/StructureDefinition/nl-core-practitioner | |
| nl-core-organizationhttp://fhir.nl/fhir/StructureDefinition/nl-core-organization |
--- We have skipped the narrative for better readability of the resource ---
</text>
</telecom>
</contact>
<description value="This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Living situation' transaction within MedMij STU3 Core." />
<purpose value="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 should be consulted." />
<copyright value="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." />
</profile>
</profile>
</profile>
</profile>
</profile>
<documentation value="Minimal requirements for a server to fulfill the 'Serve Living situation' transaction within MedMij STU3 Core (system role: MMC-LSB-zib2017/STU3-rc.3)." />
</interaction>
</searchParam>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
</interaction>
</rest>
</CapabilityStatement>
{
--- We have skipped the narrative for better readability of the resource ---
},
{
}
],
"description": "This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Living situation' 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 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.",
"xml",
"json"
],
{
},
{
},
{
},
{
},
{
}
],
{
"documentation": "Minimal requirements for a server to fulfill the 'Serve Living situation' transaction within MedMij STU3 Core (system role: MMC-LSB-zib2017/STU3-rc.3).",
{
],
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
}
],
]
}
]
}
2.2.15. Nutrition Advice (Retrieve)
This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Nutrition advice' transaction within MedMij STU3 Core.
REST Capabilities Client
| Mode | Client |
|---|---|
| Documentation | Minimal requirements for a client to fulfill the 'Retrieve Nutrition advice' transaction within MedMij STU3 Core (system role: MMC-NAR-zib2017/STU3-rc.3). |
| Search-system | Supported |
Resource Interactions
| Resource Type | SearchType | Read |
|---|---|---|
| NutritionOrder | ✓ | |
| Patient | ✓ | |
| PractitionerRole | ✓ | |
| Practitioner | ✓ | |
| Organization | ✓ |
Profiles Supported
| Name | Canonical URL |
|---|---|
| Zib NutritionAdvicehttp://nictiz.nl/fhir/StructureDefinition/zib-NutritionAdvice | |
| nl-core-patienthttp://fhir.nl/fhir/StructureDefinition/nl-core-patient | |
| nl-core-practitionerrolehttp://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole | |
| nl-core-practitionerhttp://fhir.nl/fhir/StructureDefinition/nl-core-practitioner | |
| nl-core-organizationhttp://fhir.nl/fhir/StructureDefinition/nl-core-organization |
--- We have skipped the narrative for better readability of the resource ---
</text>
</telecom>
</contact>
<description value="This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Nutrition advice' transaction within MedMij STU3 Core." />
<purpose value="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 should be consulted." />
<copyright value="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." />
</profile>
</profile>
</profile>
</profile>
</profile>
<documentation value="Minimal requirements for a client to fulfill the 'Retrieve Nutrition advice' transaction within MedMij STU3 Core (system role: MMC-NAR-zib2017/STU3-rc.3)." />
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
</interaction>
</rest>
</CapabilityStatement>
{
--- We have skipped the narrative for better readability of the resource ---
},
{
}
],
"description": "This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Nutrition advice' 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 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.",
"xml",
"json"
],
{
},
{
},
{
},
{
},
{
}
],
{
"documentation": "Minimal requirements for a client to fulfill the 'Retrieve Nutrition advice' transaction within MedMij STU3 Core (system role: MMC-NAR-zib2017/STU3-rc.3).",
{
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
}
],
]
}
]
}
2.2.16. Nutrition Advice (Serve)
This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Nutrition advice' transaction within MedMij STU3 Core.
REST Capabilities Server
| Mode | Server |
|---|---|
| Documentation | Minimal requirements for a server to fulfill the 'Serve Nutrition advice' transaction within MedMij STU3 Core (system role: MMC-NAB-zib2017/STU3-rc.3). |
| Search-system | Supported |
Resource Interactions
| Resource Type | SearchType | Read |
|---|---|---|
| NutritionOrder | ✓ | |
| Patient | ✓ | |
| PractitionerRole | ✓ | |
| Practitioner | ✓ | |
| Organization | ✓ |
Profiles Supported
| Name | Canonical URL |
|---|---|
| Zib NutritionAdvicehttp://nictiz.nl/fhir/StructureDefinition/zib-NutritionAdvice | |
| nl-core-patienthttp://fhir.nl/fhir/StructureDefinition/nl-core-patient | |
| nl-core-practitionerrolehttp://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole | |
| nl-core-practitionerhttp://fhir.nl/fhir/StructureDefinition/nl-core-practitioner | |
| nl-core-organizationhttp://fhir.nl/fhir/StructureDefinition/nl-core-organization |
--- We have skipped the narrative for better readability of the resource ---
</text>
</telecom>
</contact>
<description value="This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Nutrition advice' transaction within MedMij STU3 Core." />
<purpose value="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 should be consulted." />
<copyright value="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." />
</profile>
</profile>
</profile>
</profile>
</profile>
<documentation value="Minimal requirements for a server to fulfill the 'Serve Nutrition advice' transaction within MedMij STU3 Core (system role: MMC-NAB-zib2017/STU3-rc.3)." />
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
</interaction>
</rest>
</CapabilityStatement>
{
--- We have skipped the narrative for better readability of the resource ---
},
{
}
],
"description": "This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Nutrition advice' 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 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.",
"xml",
"json"
],
{
},
{
},
{
},
{
},
{
}
],
{
"documentation": "Minimal requirements for a server to fulfill the 'Serve Nutrition advice' transaction within MedMij STU3 Core (system role: MMC-NAB-zib2017/STU3-rc.3).",
{
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
}
],
]
}
]
}
2.2.17. Payer (Retrieve)
This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Retrieve Payer' transaction within MedMij STU3 Core.
REST Capabilities Client
| Mode | Client |
|---|---|
| Documentation | Minimal requirements for a client to fulfill the 'Retrieve Payer' transaction within MedMij STU3 Core (system role: MMC-PAR-zib2017/STU3-rc.3). |
| Search-system | Supported |
Resource Interactions
| Resource Type | SearchType | Read |
|---|---|---|
| Coverage | ✓ | |
| Patient | ✓ | |
| Organization | ✓ | |
| RelatedPerson | ✓ |
Profiles Supported
| Name | Canonical URL |
|---|---|
| Zib Payerhttp://nictiz.nl/fhir/StructureDefinition/zib-Payer | |
| nl-core-patienthttp://fhir.nl/fhir/StructureDefinition/nl-core-patient | |
| nl-core-organizationhttp://fhir.nl/fhir/StructureDefinition/nl-core-organization | |
| nl-core-relatedpersonhttp://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson |
--- We have skipped the narrative for better readability of the resource ---
</text>
</telecom>
</contact>
<description value="This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Retrieve Payer' transaction within MedMij STU3 Core." />
<purpose value="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 should be consulted." />
<copyright value="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." />
</profile>
</profile>
</profile>
</profile>
<documentation value="Minimal requirements for a client to fulfill the 'Retrieve Payer' transaction within MedMij STU3 Core (system role: MMC-PAR-zib2017/STU3-rc.3)." />
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
</interaction>
</rest>
</CapabilityStatement>
{
--- We have skipped the narrative for better readability of the resource ---
},
{
}
],
"description": "This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Retrieve Payer' 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 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.",
"xml",
"json"
],
{
},
{
},
{
},
{
}
],
{
"documentation": "Minimal requirements for a client to fulfill the 'Retrieve Payer' transaction within MedMij STU3 Core (system role: MMC-PAR-zib2017/STU3-rc.3).",
{
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
}
],
]
}
]
}
2.2.18. Payer (Serve)
This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Payer' transaction within MedMij STU3 Core.
REST Capabilities Server
| Mode | Server |
|---|---|
| Documentation | Minimal requirements for a server to fulfill the 'Serve Payer' transaction within MedMij STU3 Core (system role: MMC-PAB-zib2017/STU3-rc.3). |
| Search-system | Supported |
Resource Interactions
| Resource Type | SearchType | Read |
|---|---|---|
| Coverage | ✓ | |
| Patient | ✓ | |
| Organization | ✓ | |
| RelatedPerson | ✓ |
Profiles Supported
| Name | Canonical URL |
|---|---|
| Zib Payerhttp://nictiz.nl/fhir/StructureDefinition/zib-Payer | |
| nl-core-patienthttp://fhir.nl/fhir/StructureDefinition/nl-core-patient | |
| nl-core-organizationhttp://fhir.nl/fhir/StructureDefinition/nl-core-organization | |
| nl-core-relatedpersonhttp://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson |
--- We have skipped the narrative for better readability of the resource ---
</text>
</telecom>
</contact>
<description value="This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Payer' transaction within MedMij STU3 Core." />
<purpose value="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 should be consulted." />
<copyright value="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." />
</profile>
</profile>
</profile>
</profile>
<documentation value="Minimal requirements for a server to fulfill the 'Serve Payer' transaction within MedMij STU3 Core (system role: MMC-PAB-zib2017/STU3-rc.3)." />
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
</interaction>
</rest>
</CapabilityStatement>
{
--- We have skipped the narrative for better readability of the resource ---
},
{
}
],
"description": "This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Payer' 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 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.",
"xml",
"json"
],
{
},
{
},
{
},
{
}
],
{
"documentation": "Minimal requirements for a server to fulfill the 'Serve Payer' transaction within MedMij STU3 Core (system role: MMC-PAB-zib2017/STU3-rc.3).",
{
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
}
],
]
}
]
}
2.2.19. Pulse Rate (Retrieve)
This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Retrieve Pulse rate' transaction within MedMij STU3 Core.
REST Capabilities Client
| Mode | Client |
|---|---|
| Documentation | Minimal requirements for a client to fulfill the 'Retrieve Pulse rate' transaction within MedMij STU3 Core (system role: MMC-PRR-zib2017/STU3-rc.3). |
| Search-system | Supported |
Resource Interactions
| Resource Type | SearchType | Read |
|---|---|---|
| Observation | ✓ | |
| Patient | ✓ | |
| PractitionerRole | ✓ | |
| Practitioner | ✓ | |
| Organization | ✓ |
Search Parameters per resource type
Observation
| Name | Type | Level |
|---|---|---|
| code | token | Supported |
Patient
No search parameters are stated for this resource type
PractitionerRole
No search parameters are stated for this resource type
Practitioner
No search parameters are stated for this resource type
Organization
No search parameters are stated for this resource type
Profiles Supported
| Name | Canonical URL |
|---|---|
| Zib PulseRatehttp://nictiz.nl/fhir/StructureDefinition/zib-PulseRate | |
| nl-core-patienthttp://fhir.nl/fhir/StructureDefinition/nl-core-patient | |
| nl-core-practitionerrolehttp://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole | |
| nl-core-practitionerhttp://fhir.nl/fhir/StructureDefinition/nl-core-practitioner | |
| nl-core-organizationhttp://fhir.nl/fhir/StructureDefinition/nl-core-organization |
--- We have skipped the narrative for better readability of the resource ---
</text>
</telecom>
</contact>
<description value="This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Retrieve Pulse rate' transaction within MedMij STU3 Core." />
<purpose value="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 should be consulted." />
<copyright value="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." />
</profile>
</profile>
</profile>
</profile>
</profile>
<documentation value="Minimal requirements for a client to fulfill the 'Retrieve Pulse rate' transaction within MedMij STU3 Core (system role: MMC-PRR-zib2017/STU3-rc.3)." />
</interaction>
</searchParam>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
</interaction>
</rest>
</CapabilityStatement>
{
--- We have skipped the narrative for better readability of the resource ---
},
{
}
],
"description": "This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Retrieve Pulse rate' 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 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.",
"xml",
"json"
],
{
},
{
},
{
},
{
},
{
}
],
{
"documentation": "Minimal requirements for a client to fulfill the 'Retrieve Pulse rate' transaction within MedMij STU3 Core (system role: MMC-PRR-zib2017/STU3-rc.3).",
{
],
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
}
],
]
}
]
}
2.2.20. Pulse Rate (Serve)
This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Pulse rate' transaction within MedMij STU3 Core.
REST Capabilities Server
| Mode | Server |
|---|---|
| Documentation | Minimal requirements for a server to fulfill the 'Serve Pulse rate' transaction within MedMij STU3 Core (system role: MMC-PRB-zib2017/STU3-rc.3). |
| Search-system | Supported |
Resource Interactions
| Resource Type | SearchType | Read |
|---|---|---|
| Observation | ✓ | |
| Patient | ✓ | |
| PractitionerRole | ✓ | |
| Practitioner | ✓ | |
| Organization | ✓ |
Search Parameters per resource type
Observation
| Name | Type | Level |
|---|---|---|
| code | token | Supported |
Patient
No search parameters are stated for this resource type
PractitionerRole
No search parameters are stated for this resource type
Practitioner
No search parameters are stated for this resource type
Organization
No search parameters are stated for this resource type
Profiles Supported
| Name | Canonical URL |
|---|---|
| Zib PulseRatehttp://nictiz.nl/fhir/StructureDefinition/zib-PulseRate | |
| nl-core-patienthttp://fhir.nl/fhir/StructureDefinition/nl-core-patient | |
| nl-core-practitionerrolehttp://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole | |
| nl-core-practitionerhttp://fhir.nl/fhir/StructureDefinition/nl-core-practitioner | |
| nl-core-organizationhttp://fhir.nl/fhir/StructureDefinition/nl-core-organization |
--- We have skipped the narrative for better readability of the resource ---
</text>
</telecom>
</contact>
<description value="This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Pulse rate' transaction within MedMij STU3 Core." />
<purpose value="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 should be consulted." />
<copyright value="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." />
</profile>
</profile>
</profile>
</profile>
</profile>
<documentation value="Minimal requirements for a server to fulfill the 'Serve Pulse rate' transaction within MedMij STU3 Core (system role: MMC-PRB-zib2017/STU3-rc.3)." />
</interaction>
</searchParam>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
</interaction>
</rest>
</CapabilityStatement>
{
--- We have skipped the narrative for better readability of the resource ---
},
{
}
],
"description": "This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Pulse rate' 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 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.",
"xml",
"json"
],
{
},
{
},
{
},
{
},
{
}
],
{
"documentation": "Minimal requirements for a server to fulfill the 'Serve Pulse rate' transaction within MedMij STU3 Core (system role: MMC-PRB-zib2017/STU3-rc.3).",
{
],
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
}
],
]
}
]
}
2.2.21. Respiration (Retrieve)
This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Retrieve Respiration' transaction within MedMij STU3 Core.
REST Capabilities Client
| Mode | Client |
|---|---|
| Documentation | Minimal requirements for a client to fulfill the 'Retrieve Respiration' transaction within MedMij STU3 Core (system role: MMC-RER-zib2017/STU3-rc.3). |
| Search-system | Supported |
Resource Interactions
| Resource Type | SearchType | Read |
|---|---|---|
| Observation | ✓ | |
| DeviceUseStatement | ✓ | |
| Device | ✓ | |
| Patient | ✓ | |
| PractitionerRole | ✓ | |
| Practitioner | ✓ | |
| Organization | ✓ |
Search Parameters per resource type
Observation
| Name | Type | Level |
|---|---|---|
| code | token | Supported |
DeviceUseStatement
No search parameters are stated for this resource type
Device
No search parameters are stated for this resource type
Patient
No search parameters are stated for this resource type
PractitionerRole
No search parameters are stated for this resource type
Practitioner
No search parameters are stated for this resource type
Organization
No search parameters are stated for this resource type
Profiles Supported
| Name | Canonical URL |
|---|---|
| Zib Respirationhttp://nictiz.nl/fhir/StructureDefinition/zib-Respiration | |
| Zib Respiration AdministeredOxygen AdministrationDevicehttp://nictiz.nl/fhir/StructureDefinition/zib-Respiration-AdministeredOxygen-AdministrationDevice | |
| Zib Respiration AdministeredOxygen AdministrationDeviceProducthttp://nictiz.nl/fhir/StructureDefinition/zib-Respiration-AdministeredOxygen-AdministrationDeviceProduct | |
| nl-core-patienthttp://fhir.nl/fhir/StructureDefinition/nl-core-patient | |
| nl-core-practitionerrolehttp://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole | |
| nl-core-practitionerhttp://fhir.nl/fhir/StructureDefinition/nl-core-practitioner | |
| nl-core-organizationhttp://fhir.nl/fhir/StructureDefinition/nl-core-organization |
--- We have skipped the narrative for better readability of the resource ---
</text>
</telecom>
</contact>
<description value="This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Retrieve Respiration' transaction within MedMij STU3 Core." />
<purpose value="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 should be consulted." />
<copyright value="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." />
</profile>
<reference value="http://nictiz.nl/fhir/StructureDefinition/zib-Respiration-AdministeredOxygen-AdministrationDevice" />
</profile>
<reference value="http://nictiz.nl/fhir/StructureDefinition/zib-Respiration-AdministeredOxygen-AdministrationDeviceProduct" />
</profile>
</profile>
</profile>
</profile>
</profile>
<documentation value="Minimal requirements for a client to fulfill the 'Retrieve Respiration' transaction within MedMij STU3 Core (system role: MMC-RER-zib2017/STU3-rc.3)." />
</interaction>
</searchParam>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable by explicitly including it in the Bundle, as it is not possible for the client to retrieve the corresponding DeviceUseStatement from the Observation via a `read` (since the DeviceUseStatement references the Observation)." />
<documentation value="Strictly speaking, the `read` interaction does not need to be supported, since the server always includes this (secondary) resource in the Bundle. However, `.interaction` is mandatory (note that it is optional from R4 onwards), and `read` was deemed the most appropriate interaction." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client." />
</interaction>
</resource>
</interaction>
</rest>
</CapabilityStatement>
{
--- We have skipped the narrative for better readability of the resource ---
},
{
}
],
"description": "This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Retrieve Respiration' 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 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.",
"xml",
"json"
],
{
},
{
"reference": "http://nictiz.nl/fhir/StructureDefinition/zib-Respiration-AdministeredOxygen-AdministrationDevice",
},
{
"reference": "http://nictiz.nl/fhir/StructureDefinition/zib-Respiration-AdministeredOxygen-AdministrationDeviceProduct",
},
{
},
{
},
{
},
{
}
],
{
"documentation": "Minimal requirements for a client to fulfill the 'Retrieve Respiration' transaction within MedMij STU3 Core (system role: MMC-RER-zib2017/STU3-rc.3).",
{
],
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable by explicitly including it in the Bundle, as it is not possible for the client to retrieve the corresponding DeviceUseStatement from the Observation via a `read` (since the DeviceUseStatement references the Observation).",
{
"documentation": "Strictly speaking, the `read` interaction does not need to be supported, since the server always includes this (secondary) resource in the Bundle. However, `.interaction` is mandatory (note that it is optional from R4 onwards), and `read` was deemed the most appropriate interaction."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server includes this (secondary) resource in the Bundle, the client does not need to execute a `read`. However, since a server may choose to not include it in the Bundle, support of the `read` interaction is mandatory for a client."
}
]
}
],
]
}
]
}
2.2.22. Respiration (Serve)
This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Respiration' transaction within MedMij STU3 Core.
REST Capabilities Server
| Mode | Server |
|---|---|
| Documentation | Minimal requirements for a server to fulfill the 'Serve Respiration' transaction within MedMij STU3 Core (system role: MMC-REB-zib2017/STU3-rc.3). |
| Search-system | Supported |
Resource Interactions
| Resource Type | SearchType | Read |
|---|---|---|
| Observation | ✓ | |
| DeviceUseStatement | ✓ | |
| Device | ✓ | |
| Patient | ✓ | |
| PractitionerRole | ✓ | |
| Practitioner | ✓ | |
| Organization | ✓ |
Search Parameters per resource type
Observation
| Name | Type | Level |
|---|---|---|
| code | token | Supported |
DeviceUseStatement
No search parameters are stated for this resource type
Device
No search parameters are stated for this resource type
Patient
No search parameters are stated for this resource type
PractitionerRole
No search parameters are stated for this resource type
Practitioner
No search parameters are stated for this resource type
Organization
No search parameters are stated for this resource type
Profiles Supported
| Name | Canonical URL |
|---|---|
| Zib Respirationhttp://nictiz.nl/fhir/StructureDefinition/zib-Respiration | |
| Zib Respiration AdministeredOxygen AdministrationDevicehttp://nictiz.nl/fhir/StructureDefinition/zib-Respiration-AdministeredOxygen-AdministrationDevice | |
| Zib Respiration AdministeredOxygen AdministrationDeviceProducthttp://nictiz.nl/fhir/StructureDefinition/zib-Respiration-AdministeredOxygen-AdministrationDeviceProduct | |
| nl-core-patienthttp://fhir.nl/fhir/StructureDefinition/nl-core-patient | |
| nl-core-practitionerrolehttp://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole | |
| nl-core-practitionerhttp://fhir.nl/fhir/StructureDefinition/nl-core-practitioner | |
| nl-core-organizationhttp://fhir.nl/fhir/StructureDefinition/nl-core-organization |
--- We have skipped the narrative for better readability of the resource ---
</text>
</telecom>
</contact>
<description value="This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Respiration' transaction within MedMij STU3 Core." />
<purpose value="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 should be consulted." />
<copyright value="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." />
</profile>
<reference value="http://nictiz.nl/fhir/StructureDefinition/zib-Respiration-AdministeredOxygen-AdministrationDevice" />
</profile>
<reference value="http://nictiz.nl/fhir/StructureDefinition/zib-Respiration-AdministeredOxygen-AdministrationDeviceProduct" />
</profile>
</profile>
</profile>
</profile>
</profile>
<documentation value="Minimal requirements for a server to fulfill the 'Serve Respiration' transaction within MedMij STU3 Core (system role: MMC-REB-zib2017/STU3-rc.3)." />
</interaction>
</searchParam>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable by explicitly including it in the Bundle, as it is not possible for the client to retrieve the corresponding DeviceUseStatement from the Observation via a `read` (since the DeviceUseStatement references the Observation)." />
<documentation value="Strictly speaking, the `read` interaction does not need to be supported, since the server always includes this (secondary) resource in the Bundle. However, `.interaction` is mandatory (note that it is optional from R4 onwards), and `read` was deemed the most appropriate interaction." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
<documentation value="This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle." />
<documentation value="If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional." />
</interaction>
</resource>
</interaction>
</rest>
</CapabilityStatement>
{
--- We have skipped the narrative for better readability of the resource ---
},
{
}
],
"description": "This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Respiration' 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 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.",
"xml",
"json"
],
{
},
{
"reference": "http://nictiz.nl/fhir/StructureDefinition/zib-Respiration-AdministeredOxygen-AdministrationDevice",
},
{
"reference": "http://nictiz.nl/fhir/StructureDefinition/zib-Respiration-AdministeredOxygen-AdministrationDeviceProduct",
},
{
},
{
},
{
},
{
}
],
{
"documentation": "Minimal requirements for a server to fulfill the 'Serve Respiration' transaction within MedMij STU3 Core (system role: MMC-REB-zib2017/STU3-rc.3).",
{
],
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable by explicitly including it in the Bundle, as it is not possible for the client to retrieve the corresponding DeviceUseStatement from the Observation via a `read` (since the DeviceUseStatement references the Observation).",
{
"documentation": "Strictly speaking, the `read` interaction does not need to be supported, since the server always includes this (secondary) resource in the Bundle. However, `.interaction` is mandatory (note that it is optional from R4 onwards), and `read` was deemed the most appropriate interaction."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
},
{
"documentation": "This is a secondary resource that needs to be resolvable, either by supporting a `read` interaction or explicitly including it in the Bundle.",
{
"documentation": "If the server always includes this (secondary) resource in the Bundle, support of the `read` interaction is optional."
}
]
}
],
]
}
]
}