3.3. 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.
3.3.1. Encounter (Retrieve)
This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Retrieve Encounter' transaction within Long-term Healthcare.
REST Capabilities Client
| Mode | Client |
|---|---|
| Documentation | Minimal requirements for a client to fulfill the 'Retrieve Encounter' transaction within Long-term Healthcare (system role: LZ-ENR-beta.3). |
| Search-system | Supported |
Resource Interactions
| Resource Type | SearchType | Read |
|---|---|---|
| Encounter | ✓ | |
| Patient | ✓ | |
| PractitionerRole | ✓ | |
| Practitioner | ✓ | |
| Organization | ✓ | |
| Condition | ✓ | |
| Procedure | ✓ |
Profiles Supported
| Name | Canonical URL |
|---|---|
| LzEncounterhttp://medmij.nl/fhir/StructureDefinition/lz-Encounter | |
| 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 | |
| Zib Problemhttp://nictiz.nl/fhir/StructureDefinition/zib-Problem | |
| Zib Procedurehttp://nictiz.nl/fhir/StructureDefinition/zib-Procedure |
--- 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 Encounter' transaction within Long-term Healthcare." />
<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>
</profile>
</profile>
<documentation value="Minimal requirements for a client to fulfill the 'Retrieve Encounter' transaction within Long-term Healthcare (system role: LZ-ENR-beta.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>
<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 Encounter' transaction within Long-term Healthcare.",
"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 Encounter' transaction within Long-term Healthcare (system role: LZ-ENR-beta.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."
}
]
},
{
"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."
}
]
}
],
]
}
]
}
3.3.2. Encounter (Serve)
This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Encounter' transaction within Long-term Healthcare.
REST Capabilities Server
| Mode | Server |
|---|---|
| Documentation | Minimal requirements for a server to fulfill the 'Serve Encounter' transaction within Long-term Healthcare (system role: LZ-ENB-beta.3). |
| Search-system | Supported |
Resource Interactions
| Resource Type | SearchType | Read |
|---|---|---|
| Encounter | ✓ | |
| Patient | ✓ | |
| PractitionerRole | ✓ | |
| Practitioner | ✓ | |
| Organization | ✓ | |
| Condition | ✓ | |
| Procedure | ✓ |
Profiles Supported
| Name | Canonical URL |
|---|---|
| LzEncounterhttp://medmij.nl/fhir/StructureDefinition/lz-Encounter | |
| 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 | |
| Zib Problemhttp://nictiz.nl/fhir/StructureDefinition/zib-Problem | |
| Zib Procedurehttp://nictiz.nl/fhir/StructureDefinition/zib-Procedure |
--- 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 Encounter' transaction within Long-term Healthcare." />
<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>
</profile>
</profile>
<documentation value="Minimal requirements for a server to fulfill the 'Serve Encounter' transaction within Long-term Healthcare (system role: LZ-ENB-beta.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>
<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 Encounter' transaction within Long-term Healthcare.",
"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 Encounter' transaction within Long-term Healthcare (system role: LZ-ENB-beta.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."
}
]
},
{
"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."
}
]
}
],
]
}
]
}
3.3.3. Nursing Report (Retrieve)
This CapabilityStatement describes the minimal requirements for a client to fulfill the 'Retrieve Nursing report' transaction within Long-term Healthcare.
REST Capabilities Client
| Mode | Client |
|---|---|
| Documentation | Minimal requirements for a client to fulfill the 'Retrieve Nursing report' transaction within Long-term Healthcare (system role: LZ-NRR-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 |
|---|---|
| LzNursingReporthttp://medmij.nl/fhir/StructureDefinition/lz-NursingReport | |
| 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 Nursing report' transaction within Long-term Healthcare." />
<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 Nursing report' transaction within Long-term Healthcare (system role: LZ-NRR-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 Nursing report' transaction within Long-term Healthcare.",
"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 Nursing report' transaction within Long-term Healthcare (system role: LZ-NRR-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."
}
]
}
],
]
}
]
}
3.3.4. Nursing Report (Serve)
This CapabilityStatement describes the minimal requirements for a server to fulfill the 'Serve Nursing report' transaction within Long-term Healthcare.
REST Capabilities Server
| Mode | Server |
|---|---|
| Documentation | Minimal requirements for a server to fulfill the 'Serve Nursing report' transaction within Long-term Healthcare (system role: LZ-NRB-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 |
|---|---|
| LzNursingReporthttp://medmij.nl/fhir/StructureDefinition/lz-NursingReport | |
| 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 Nursing report' transaction within Long-term Healthcare." />
<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 Nursing report' transaction within Long-term Healthcare (system role: LZ-NRB-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 Nursing report' transaction within Long-term Healthcare.",
"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 Nursing report' transaction within Long-term Healthcare (system role: LZ-NRB-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."
}
]
}
],
]
}
]
}