This fragment is available on implementation.html
| Type | Reference | Content |
|---|---|---|
| web | github.com |
The OR behavior for repeated expressions of one type follows the Bulk Data export specification
. Search result controls _summary
and _elements
are rejected inside _typeFilter
, including when appended through a Patient chain.
|
| web | profiles.ihe.net |
What may be asked for.
The exportable resource types and the search parameters usable in _type
and _typeFilter
are bounded by the EHDS priority data categories for primary use and their European FHIR profiles ( HL7 Europe Base and Core
, HL7 Europe Laboratory Report
, HL7 Europe Imaging Report
). Where a resource type is covered by an IHE QEDm
named option, its PCC-44
search parameter combinations are reused, so a data holder that already implements QEDm for primary use needs no second query surface.
|
| web | profiles.ihe.net |
What may be asked for.
The exportable resource types and the search parameters usable in _type
and _typeFilter
are bounded by the EHDS priority data categories for primary use and their European FHIR profiles ( HL7 Europe Base and Core
, HL7 Europe Laboratory Report
, HL7 Europe Imaging Report
). Where a resource type is covered by an IHE QEDm
named option, its PCC-44
search parameter combinations are reused, so a data holder that already implements QEDm for primary use needs no second query surface.
|
| web | eur-lex.europa.eu | Secondary-use data categories ( Regulation (EU) 2025/327 , Article 51). These are the legal categories of electronic health data that a data permit may cover. Nearly everything exported through this guide falls in electronic health data from EHRs (Article 51(1)(a)); dispensing data also falls in healthcare-related administrative data, including dispensation, claims and reimbursement data (Article 51(1)(e)). An Article 51 category says nothing about structure and is not something a client can request over the wire. |
| web | github.com |
Organisation- and system-level authentication follows GF Authentication
: OAuth 2.0 with the FAPI 2.0 security profile, private_key_jwt
client authentication, sender-constrained access tokens, and mTLS transport. Because secondary use is attributable to a named researcher
and not only to an organisation, the Bulk Export Client SHALL additionally establish the identity of that natural person through the VAD
( Vertrouwde AuthenticatieDienst
) over OpenID Connect, in the pattern implemented by the MGO DVP Proxy
. That subject identity SHALL be carried into the token request and recorded in the AuditEvent
of every transaction on this page.
|
| web | profiles.ihe.net |
All exchanges SHALL use TLS 1.2 or later. Both the Bulk Export Client and the Bulk Export Server SHALL record AuditEvent
resources following the BALP
patterns, for kick-off, status and export requests, including the data permit identifier and the VAD-established researcher identity.
|