EEHRxF Document Access Provider - Document Submission Option. CapabilityStatement for the Document Submission Option on the EEHRxF Document Access Provider.This option enables the Access Provider to receive documents from external DocumentPublishers via [ITI-105 Simplified Publish](https://profiles.ihe.net/ITI/MHD/ITI-105.html).Systems implementing this option:- SHALL also implement the base [Document Access Provider](CapabilityStatement-EEHRxF-DocumentAccessProvider.html) capabilities- SHALL accept ITI-105 transactions from authorized Document Publishers- SHALL make received documents available via ITI-67 and ITI-68- SHALL validate documents against EEHRxF content profilesThis option is REQUIRED when acting as a delegated access provider for externalDocument Publishers (e.g., integration engines, national infrastructure).### Actor GroupingAdds to base Document Access Provider:- [MHD Document Recipient](https://profiles.ihe.net/ITI/MHD/1331_actors_and_transactions.html) - Simplified Publish Option ([CapabilityStatement](https://profiles.ihe.net/ITI/MHD/CapabilityStatement-IHE.MHD.DocumentRecipient.html))### Transaction| Transaction | Description | Optionality ||-------------|-------------|-------------|| ITI-105 Simplified Publish | Accept document publication from Document Publishers | R |### SecuritySystems SHALL support SMART Backend Services authorization for document submission.EEHRxFDocumentAccessProviderSubmissionOption: (2 methods)
Accept DocumentReference with embedded document (ITI-105 Simplified Publish).The DocumentReference SHALL include:- status (required)- type (required - LOINC document type)- subject (required - Patient reference)- content.attachment.contentType (required)- content.attachment.data (required - base64-encoded document content)The server SHALL:- Validate against EEHRxF DocumentReference profile- Extract and persist the document- For FHIR Documents, ensure the content is retrievable as a native FHIR Document Bundle (not wrapped in Binary)- Assign server-generated IDs- Return 201 Created with the persisted DocumentReference. Profile: http://hl7.eu/fhir/health-data-api/StructureDefinition/EehrxfMhdDocumentReferenceDocumentReference_create <in> <out>
Pre-validation of DocumentReference before submissionDocumentReference_op_validate <in> <out>

EEHRxF Document Access Provider CapabilityStatement. CapabilityStatement for the EEHRxF Document Access Provider actor. This composite actorprovides access to EEHRxF FHIR Documents by serving them to Document Consumers via query APIs.### Actor GroupingThis composite actor groups the following IHE actors:- [IUA Authorization Server](https://profiles.ihe.net/ITI/IUA/index.html#34112-authorization-server)- [IUA Resource Server](https://profiles.ihe.net/ITI/IUA/index.html#34113-resource-server)- [PDQm Patient Demographics Supplier](https://profiles.ihe.net/ITI/PDQm/volume-1.html)- [MHD Document Responder](https://profiles.ihe.net/ITI/MHD/1331_actors_and_transactions.html)### Transactions| Transaction | Description | Optionality ||-------------|-------------|-------------|| ITI-67 Find Document References | Respond to document metadata queries from Document Consumers | R || ITI-68 Retrieve Document | Serve document content to Document Consumers | R || ITI-78 Patient Demographics Query | Respond to patient demographics queries | R || Get Access Token | Issue authorization tokens to clients | R |### SecuritySystems SHALL support SMART Backend Services authorization for all transactions.### Document Submission OptionTo accept document publication from external Document Publishers, implement the[Document Submission Option](CapabilityStatement-EEHRxF-DocumentAccessProvider-SubmissionOption.html).### DeploymentThe Document Access Provider may be grouped with Document Publisher, in which casedocument publication is internal. See the[grouped Document Publisher/Access Provider CapabilityStatement](CapabilityStatement-EEHRxF-DocumentPublisherAccessProvider.html)for this deployment pattern.EEHRxFDocumentAccessProvider: (6 methods)
Read DocumentReference by logical ID. Profile: http://hl7.eu/fhir/health-data-api/StructureDefinition/EehrxfMhdDocumentReferenceDocumentReference_read_1 <in> <out>
Search for DocumentReference resources (ITI-67). Profile: http://hl7.eu/fhir/health-data-api/StructureDefinition/EehrxfMhdDocumentReferenceDocumentReference_search_type_1 <in> <out>
Retrieve document content (ITI-68)Binary_read_1 <in> <out>
Read Patient by logical ID. Profile: http://hl7.eu/fhir/base/StructureDefinition/patient-eu-corePatient_read_2 <in> <out>
Search for patients (PDQm ITI-78). Profile: http://hl7.eu/fhir/base/StructureDefinition/patient-eu-corePatient_search_type_2 <in> <out>
System-wide search supportsearch_system_1 <in> <out>

EEHRxF Grouped Document Publisher/Access Provider CapabilityStatement. CapabilityStatement for the grouped EEHRxF Document Publisher and Document Access Provideractors. This represents a deployment where document production and access provision areco-located in the same system.### Deployment PatternThis CapabilityStatement applies when:- An EHR system both produces documents AND provides access to them- Document publication is handled internally- External clients only need to query and retrieve documentsIn this grouped deployment, document publication is internal to the system and not exposedexternally. The external API provides only document discovery (ITI-67) and retrieval (ITI-68)capabilities.### Actor GroupingThis grouped actor combines:- **Document Publisher** (internal) - Produces and stores documents internally- **Document Access Provider** (external-facing) - Serves documents to Document ConsumersThe underlying IHE actors are:- [IUA Authorization Server](https://profiles.ihe.net/ITI/IUA/index.html#34112-authorization-server)- [IUA Resource Server](https://profiles.ihe.net/ITI/IUA/index.html#34113-resource-server)- [PDQm Patient Demographics Supplier](https://profiles.ihe.net/ITI/PDQm/volume-1.html)- [MHD Document Responder](https://profiles.ihe.net/ITI/MHD/1331_actors_and_transactions.html)Note: MHD Document Recipient is not listed because publication is internal.### External Transactions| Transaction | Description | Optionality ||-------------|-------------|-------------|| ITI-67 Find Document References | Respond to document metadata queries from Document Consumers | R || ITI-68 Retrieve Document | Serve document content to Document Consumers | R || ITI-78 Patient Demographics Query | Respond to patient demographics queries | R || Get Access Token | Issue authorization tokens to clients | R |### SecuritySystems SHALL support SMART Backend Services authorization for all transactions.### When to Use This CapabilityStatementUse this CapabilityStatement when implementing:- Hospital EHR systems that produce and serve their own documents- Regional health information exchanges with integrated document repositories- Any system where document creation and access are tightly coupledFor systems that need to receive documents from external sources, use the[Document Access Provider with Document Submission Option](CapabilityStatement-EEHRxF-DocumentAccessProvider-SubmissionOption.html).EEHRxFDocumentPublisherAccessProvider: (6 methods)
Read DocumentReference by logical ID. Profile: http://hl7.eu/fhir/health-data-api/StructureDefinition/EehrxfMhdDocumentReferenceDocumentReference_read_2 <in> <out>
Search for DocumentReference resources (ITI-67). Profile: http://hl7.eu/fhir/health-data-api/StructureDefinition/EehrxfMhdDocumentReferenceDocumentReference_search_type_2 <in> <out>
Retrieve document content (ITI-68)Binary_read_2 <in> <out>
Read Patient by logical ID. Profile: http://hl7.eu/fhir/base/StructureDefinition/patient-eu-corePatient_read_3 <in> <out>
Search for patients (PDQm ITI-78). Profile: http://hl7.eu/fhir/base/StructureDefinition/patient-eu-corePatient_search_type_3 <in> <out>
System-wide search supportsearch_system_2 <in> <out>

EEHRxF Resource Access Provider CapabilityStatement. CapabilityStatement for the EEHRxF Resource Access Provider actor. This actor servesclinical data resources following the International Patient Access (IPA) patterns andIHE QEDm Clinical Data Source capabilities.This CapabilityStatement defines the capabilities for systems providing direct resourceaccess (beyond document-based exchange) in the EU EHR Exchange Format (EEHRxF) ecosystem.It inherits patterns from:- **IPA (International Patient Access)**: Resource profiles and search parameter patterns- **IHE QEDm (Query for Existing Data for Mobile)**: Clinical Data Source actor capabilities### Resource Flexibility (IPA Alignment)Following IPA's approach, servers are not required to support all clinical resources listedbelow. Servers MAY choose which resources to implement based on their capabilities and usecases. The only required resource is Patient (for lookup context). This flexibilityencourages partial implementations, allowing more servers to participate even if they onlysupport EU Core for certain resource types.**Required**: Patient (for lookup context)**Recommended (choose based on capabilities)**:- Practitioner, Organization: Reference resolution- Condition, AllergyIntolerance: Patient safety data- Observation, DiagnosticReport: Clinical results- MedicationRequest, MedicationDispense, MedicationStatement: Medication data- Immunization: Vaccination records- Encounter: Visit contextThe server's CapabilityStatement declares which resources are actually supported.### SecuritySystems SHALL support SMART Backend Services authorization for all transactions.### Profile InheritanceResources SHOULD conform to EU Core profiles where available.EEHRxFResourceAccessProvider_1: (22 methods)
Read Patient by logical ID. Profile: http://hl7.eu/fhir/base/StructureDefinition/patient-eu-corePatient_read_4 <in> <out>
Search for patients for lookup purposes. Profile: http://hl7.eu/fhir/base/StructureDefinition/patient-eu-corePatient_search_type_4 <in> <out>
Read Practitioner by logical IDPractitioner_read_1 <in> <out>
Read Organization by logical IDOrganization_read_1 <in> <out>
Read Condition by logical IDCondition_read_1 <in> <out>
Search for Condition resourcesCondition_search_type_1 <in> <out>
Read AllergyIntolerance by logical IDAllergyIntolerance_read_1 <in> <out>
Search for AllergyIntolerance resourcesAllergyIntolerance_search_type_1 <in> <out>
Read Observation by logical IDObservation_read_1 <in> <out>
Search for Observation resourcesObservation_search_type_1 <in> <out>
Read DiagnosticReport by logical IDDiagnosticReport_read_1 <in> <out>
Search for DiagnosticReport resourcesDiagnosticReport_search_type_1 <in> <out>
Read MedicationRequest by logical IDMedicationRequest_read_1 <in> <out>
Search for MedicationRequest resourcesMedicationRequest_search_type_2 <in> <out>
Read MedicationDispense by logical IDMedicationDispense_read_1 <in> <out>
Search for MedicationDispense resourcesMedicationDispense_search_type_1 <in> <out>
Read Immunization by logical IDImmunization_read <in> <out>
Search for Immunization resourcesImmunization_search_type <in> <out>
Read MedicationStatement by logical IDMedicationStatement_read <in> <out>
Search for MedicationStatement resourcesMedicationStatement_search_type <in> <out>
Read Encounter by logical IDEncounter_read_1 <in> <out>
Search for Encounter resourcesEncounter_search_type_1 <in> <out>
Slices: hl7.fhir.eu.health-data-api