| Package | hl7.fhir.uv.ehrs-rle |
| Type | CapabilityStatement |
| Id | conformance-ehrs-rle |
| FHIR Version | R6 |
| Source | http://hl7.org/fhir/uv/ehrs-rle/https://build.fhir.org/ig/HL7/ehrs-rle-ig/CapabilityStatement-conformance-ehrs-rle.html |
| URL | http://hl7.org/fhir/uv/ehrs-rle/CapabilityStatement/conformance-ehrs-rle |
| Version | 1.2.0 |
| Status | draft |
| Date | 2025-01-30T16:34:01+00:00 |
| Name | EHRSFunctionalModelRecordLifecycleEventsCapabilityStatement |
| Title | EHRS Functional Model - Record Lifecycle Events - Capability Statement |
| Realm | uv |
| Authority | hl7 |
| Description | This profile defines the expected capabilities of an ''Electronic Health Record System'' when conforming to the EHRS functional model's Record Lifecycle specification. |
| Kind | requirements |
No resources found
| StructureDefinition | |
| ehrsrle-auditevent | EHRS Functional Model - Record Lifecycle Events - AuditEvent |
| ehrsrle-provenance | EHRS Functional Model - Record Lifecycle Events - Provenance |
Note: links and images are rebased to the (stated) source
Generated Narrative: CapabilityStatement conformance-ehrs-rle
FHIRxml, jsonNote to Implementers: FHIR Capabilities
Any FHIR capability may be 'allowed' by the system unless explicitly marked as 'SHALL NOT'. A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.
clientConformant systems must record [[Provenance]] records on all Create, Update and Delete actions on any resource other than Provenance or AuditEvent. Conformant systems must record [[AuditEvent]] records on all Create, Update and Delete actions as well as all GET operations (read, search, etc.)
Any security rules??
The summary table lists the resources that are part of this configuration, and for each resource it lists:
_include_revinclude| Resource Type | Profile | R | S | U | C | Searches | _include | _revinclude | Operations |
|---|---|---|---|---|---|---|---|---|---|
| Provenance | http://hl7.org/fhir/uv/ehrs-rle/StructureDefinition/ehrsrle-provenance | y | |||||||
| AuditEvent | http://hl7.org/fhir/uv/ehrs-rle/StructureDefinition/ehrsrle-auditevent | y |
createAllows defining a new data element. Repositories requiring curation of submitted data elements may require all new data elements to have a status of 'draft'.
createAllows defining a new data element. Repositories requiring curation of submitted data elements may require all new data elements to have a status of 'draft'.
{
"resourceType": "CapabilityStatement",
"id": "conformance-ehrs-rle",
"text": {
"status": "extensions",
"div": "<!-- snip (see above) -->"
},
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode": "ehr"
},
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
"valueInteger": 1,
"_valueInteger": {
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical": "http://hl7.org/fhir/uv/ehrs-rle/ImplementationGuide/hl7.fhir.uv.ehrs-rle"
}
]
}
},
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
"valueCode": "informative",
"_valueCode": {
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical": "http://hl7.org/fhir/uv/ehrs-rle/ImplementationGuide/hl7.fhir.uv.ehrs-rle"
}
]
}
}
],
"url": "http://hl7.org/fhir/uv/ehrs-rle/CapabilityStatement/conformance-ehrs-rle",
"version": "1.2.0",
"name": "EHRSFunctionalModelRecordLifecycleEventsCapabilityStatement",
"title": "EHRS Functional Model - Record Lifecycle Events - Capability Statement",
"status": "draft",
"date": "2025-01-30T16:34:01+00:00",
"publisher": "HL7 International / Electronic Health Records",
"contact": [
{
"telecom": [
{
"system": "url",
"value": "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description": "This profile defines the expected capabilities of an ''Electronic Health Record System'' when conforming to the EHRS functional model's Record Lifecycle specification.",
"jurisdiction": [
{
"coding": [
{
"system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code": "001"
}
]
}
],
"kind": "requirements",
"fhirVersion": "6.0.0-ballot2",
"format": [
"xml",
"json"
],
"rest": [
{
"mode": "client",
"documentation": "Conformant systems must record [[Provenance]] records on all Create, Update and Delete actions on any resource other than Provenance or AuditEvent. Conformant systems must record [[AuditEvent]] records on all Create, Update and Delete actions as well as all GET operations (read, search, etc.)",
"security": {
"description": "Any security rules??"
},
"resource": [
{
"type": "Provenance",
"profile": "http://hl7.org/fhir/uv/ehrs-rle/StructureDefinition/ehrsrle-provenance",
"interaction": [
{
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
"valueCode": "SHALL"
}
],
"code": "create",
"documentation": "Allows defining a new data element. Repositories requiring curation of submitted data elements may require all new data elements to have a status of 'draft'."
}
]
},
{
"type": "AuditEvent",
"profile": "http://hl7.org/fhir/uv/ehrs-rle/StructureDefinition/ehrsrle-auditevent",
"interaction": [
{
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
"valueCode": "SHALL"
}
],
"code": "create",
"documentation": "Allows defining a new data element. Repositories requiring curation of submitted data elements may require all new data elements to have a status of 'draft'."
}
]
}
]
}
]
}