The table below shows recommended sets of API endpoints to be implemented depending on your use of services: 

                                  Service in use

API endpoint \ 

Recommended for Patient & SearchRecommended for Patient & Search, download RegistryMandatory for ConnectMandatory for Connect, Download RegistryPhase 1Phase 2Document?Comment
SEARCH & MATCH
PATIENTS
​/patients [POST]yesnoyes (PR)yes (PR)x


​/patients [PUT]nonoyes (PR)nox


​/patients/list [GET]nonononox

Search & Match Service Graphical User Interface (GUI) content, optional for participating organisations
​/patients​/{wmdaId} [GET]nononono (but strongly recommended)x

Search & Match Service GUI content, optional for participating organisations
/patients/status [PUT]yesnononox

Recommended if search results need to stay up-to-date. In that case patient status can be set to "ACT" in Search & Match.
​/patients​/user [PUT]nonononox

Search & Match Service GUI content, optional for participating organisations
SEARCH
/searches [POST]yesnoyes (PR)nox


/searches/patientSearches/{wmdaId} [GET]yesnoyes (PR)nox


/searches/refreshAllPatientSearches [POST]nonononox

Not required. Search results will stay up-to-date if patient status is set to "ACT" in Search & Match.
/searches/{searchId} [GET]nonononox

Highly recommended

/searches/searchResultsRefresh [POST]

nonononox

Not required. Search results will stay up-to-date if patient status is set to "ACT" in Search & Match. 
/searches/searchResults/donors [POST]yesnoyes (PR)nox

At least one of those is mandatory, 
/searches/searchResults/cbus [POST]x

/searches/{searchId}/searchResults/adcu [POST]


​/searches​/{searchId}​/searchResults​/registries [GET]nonononox

Search & Match Service GUI content, optional for participating organisations
/searches/{searchId}/searchResults/cbbs [GET]nonononox

Search & Match Service GUI content, optional for participating organisations
/searches/selected/donors [POST]nonononox

Search & Match Service GUI content, optional for participating organisations
​/searches​/selected​/cbus [POST]nonononox

Search & Match Service GUI content, optional for participating organisations
/searches/donors/{searchResultsId} [GET]nonononox

Search & Match Service GUI content, optional for participating organisations
​/searches​/cbus​/{searchResultsId} [GET]nonononox

Search & Match Service GUI content, optional for participating organisations
DASHBOARD
for allnonononox

Search & Match Service GUI content, optional for participating organisations
CONNECT API
ATTACHMENT
​/api​/v2​/attachmentTicket [POST]

nono


Optional for participating organisations
/api/v2/attachmentDownloadURL [POST]

nono


Optional for participating organisations
​/api​/v12/attachmentDownloadedNotification [POST]

nono


Optional for participating organisations
RETRIEVE
​/api​/v2​/availableMessages [GET]

yesyesx

Mandatory so individual endpoints will only be called if there is a message available at that endpoint. 
/api/v2/availableMessagesAll [POST]






Not implemented - Will only implement if early adopters request
/api/v2/recoverMessages [POST]

nonox

Optional
ADMIN
/api/v2/alertRetrieve [POST]

nonox
deferRecommended
/api/v2/alertUpdateRetrieve [POST]

nonox

Recommended
PATIENT
/api/v2/updateRegisteredPatient [POST]

yes (PR)yes (PR)x
defer
​/api​/v2​/updateRegisteredPatientRetrieve [POST]

yes (DR)yes (DR)x


PING
​/api​/v2​/pingRequest [POST]

nonox

Optional for participating organisations
/api/v2/pingRetrieve [POST]

nonox

Optional for participating organisations
TEXT MESSAGE
/api/v2/textMessageRequest [POST]

nonox

Optional for participating organisations
​/api​/v2​/TextMessageRetrieve [POST]

nonox

Optional for participating organisations
REQUEST
/api/v2/genericRequestRequest [POST]

nonox
x
/api/v2/genericRequestRetrieve [POST]

nonox


/api/v2/extendedTypingRequestRequest [POST]

yes (PR)yes (PR)x
x
/api/v2/extendedTypingRequestRetrieve [POST]

nonox

recommended for DCs  or CBBs with incompletely typed donors / cbus
/api/v2/extendedTypingResponseRequest [POST]

nonox
xrecommended for DCs with incompletely typed donors
/api/v2/extendedTypingResponseRetrieve [POST]

yes (PR)yes (PR)x


/api/v2/extendedTypingResponseRequestCbu [POST]

nono
xxrecommended for CBBs with incompletely typed cbus
/api/v2/extendedTypingResponseRetrieveCbu [POST]

yes (PR)yes (PR)
x

​/api​/v2/sampleRequestRequest [POST]

yes (PR)yes (PR)x
x
​/api​/v2/sampleRequestRetrieve [POST]

yes (DR, CBB)yes (DR, CBB)x


​/api​/v2​/sampleInfoRequest [POST]

yes (DR, CBB)yes (DR, CBB)x
x
​/api​/v2/sampleInfoRetrieve [POST]

yes (PR)yes (PR)x


​/api​/v2/sampleArrivalRequest [POST]

yes (DR, CBB)yes (DR, CBB)x
x
​/api​/v2/sampleArrivalRetrieve [POST]

yes (PR)yes (PR)x


/api/v2/sampleResponseRequest [POST]

yes (PR)yes (PR)x
x
/api/v2/sampleResponseRetrieve [POST]

yes (DR, CBB)yes (DR, CBB)x


/api/v2/infectiousDiseaseMarkerRequest [POST]

yes (PR)yes (PR)x
x
/api/v2/infectiousDiseaseMarkerRequestRetrieve [POST]

yes (DR)yes (DR)x


​/api​/v2/infectiousDiseaseMarkerResultRequest [POST]

yes (DR)yes (DR)x
x
/api/v2/infectiousDiseaseMarkerResultRetrieve [POST]

yes (PR)yes (PR)x


/api/v2/infectiousDiseaseMarkerCbuResultRequest [POST]

yes (CBB)yes (CBB)
xx
/api/v2/infectiousDiseaseMarkerCbuResultRetrieve [POST]

yes (PR)yes (PR)
x

​/api​/v2​/reservationRequestRequest [POST]

no (PR)no (PR)x
xreservations are mandatory upon any other request
​/api​/v2​/reservationRequestRetrieve [POST]

yes (DR)yes (DR)x


​/api​/v2/reservationResponseRequest [POST]

yes (DR)yes (DR)x
x
/api/v2/reservationResponseRetrieve [POST]

yes (PR)yes (PR)x

reservation response will be sent after every request
/api/v2/reservationCbuResponseRequest [POST]

yes (CBB)yes (CBB)
xx
/api/v2/reservationCbuResponseRetrieve [POST]

yes (PR)yes (PR)
x

​/api​/v2​/reservationReleaseRequest [POST]

yes (PR)yes (PR)x
x
​/api​/v2​/reservationReleaseRetrieve [POST]

yes (DR)yes (DR)x


/api/v2/requestCancellationRequest [POST]

yes (PR)yes (PR)x
x
/api/v2/requestCancellationRetrieve [POST]

yes (DR)yes (DR)x


​/api​/v2/requestRejectedRequest [POST]

yes (DR)yes (DR)x
x
/api/v2/requestRejectedRetrieve [POST]

yes (PR)yes (PR)x


​/api​/v2​/resultReminderRequest [POST]

nonox
xrecommended
/api/v2/resultReminderRetrieve [POST]

nonox

recommended
GENERAL
/api/v2/messageResponse [POST]

yesyesx


​/api​/v2​/messageResponseRetrieve [POST]

yesyesx


CBU







/api/v2/cordBloodUnitReportRequestRequest [POST]

nono

xshould be generalised to CBU and ADCUs, etc...
/api/v2/cordBloodUnitReportRequestRetrieve [POST]

yes (CBB)yes (CBB)



/api/v2/cordBloodUnitReportResponseRequest [POST]

yes (CBB)yes (CBB)

x
​/api​/v2/cordBloodUnitReportResponseRetrieve [POST]

nono




Change log new semantics April 2025:


CBU endpoints and responses

The semantics now include the specifications of the CBU endpoints. This also includes a specific endpoint as a response to the ExtendedTypingRequest and the InfectiousDiseaseMarkerRequest. See next paragraph. 


ExtendedTypingResponse and InfectiousDiseaseMarkerResult splitted to CBU and Adult donor specific endpoints

Before there was one endpoint available as a response for the ExtendedTypingRequest and one endpoint as a response to the InfectiousDiseaseMarkerRequest. In the new version of the semantics there are now separate endpoints for the CBU (Cord's) and (Adult) donors. This means the following endpoints are added to the semantics:


Document Exchange

Following the RFC (link), the semantics now include the specifications for (general) document exchange. The semantics hold four new general endpoints to accommodate document exchange, including:

and four endpoints for sending and retrieving cordBloodUnitReport(s), with specific endpoints: 


Attachment block added to existing and new endpoints

To provide the possibility to exchange the information of an attachment together with the request/response message send to the receiving registry of an attachment that is uploaded, and can be downloaded by the receiving registry, in the semantics an attachment block is added to some of the endpoints.


ExtendedTypingResponse HLA information

The HLA block is now included in the response block of the extendedtypingresponse. The block itself is required, whereas the fields within the block are not technically required as this is dependent on the request.


Field name harmonization for consistency

Fields within the ExtendedTyping and InfectiousDiseaseMarker endpoints were harmonized to align with the fields as mentioned within other endpoints. 


Sample response, addition of ccr5

The ccr5 field is added to the response block of the sampleResponse endpoint.







  • No labels