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.