...
| Field | Details |
|---|---|
| messageId | string($uuid) |
| sentAtUtc | string($date-time) Server-supplied timestamp showing UTC time of Message delivery to recipient's inbox queue. |
| sender | string maximum: 9999 minimum: 0 maxLength: 4 minLength: 4 example: 5678 4 digit ION of sender |
| messageType | string Enum: |
6.1.2 Embedded Address block
...
(NEW_ADD
...
)
With this message block, the contact information of the hub's institutions, namely Financial institutions, Transplant Centers and Laboratories are shared with the partner hubs. Thus a partner hub has all the required contact information for the Institution contained in Donor Requests.
...
Suggested format | Suggested field | Description | Mapping to NEW_ADD |
StringType | city | The name of the city, town, suburb, village or other community or delivery center. | City CITY Req 40 |
StringType | country | Country - a nation as commonly understood or generally accepted. | Country COUNTRY Req 2 |
StringType | district | The name of the administrative area (county). | Address Line 2 ADDR_2 Opt 40 |
List <StringType><StringType> | line | This component contains the house number, apartment number, street name, street direction, P.O. | Address Line 3 ADDR_3 Opt 40 |
Period | period | Time period when address was/is in use. | new - Opt |
StringType | postalCode | A postal code designating a region defined by the postal service. | ZIP code ZIP Req 10 |
StringType | state | Sub-unit of a country with limited sovereignty in a federally organized country. | new - Opt |
StringType | text | Specifies the entire address as it should be displayed e.g. on a postal label. This may be provided instead of or as well as the specific parts. | Address Line 1 to Address Line 3, City, Country, Zip code - Opt |
Enumeration <Address<Address.AddressType>AddressType> | type | Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses. Most addresses are both.). This is the underlying object with id, value and extensions. The accessor "getType" gives direct access to the value. | new - Req |
Enumeration <Address<Address.AddressUse>AddressUse> | use | The purpose of this address. | Institution Type INST_TYPE Req 3 |
StringType | contactPerson | The name of the contact person. | Contact person PERSON Opt 40 |
StringType |
| The value is a telephone number used for voice calls. | Phone Number PHONE Req 20 |
StringType |
| The value is a fax machine. | Fax Number FAX Opt 20 |
StringType |
| The value is an email address. | Email address EMAIL Opt 60 |
Not needed anymore, as the full address will be sent embedded in every request. | INST_ID Req 10 | ||
Obsolete. Accreditation is provided by S&M on the match list. | Accreditation Opt 5 |
6.1.3 Embedded Patient Block
There is no "register patient" endpoint. Instead, an embedded patient block will accompany all requests. The embedded patient block looks as follows:
...
In EMDIS, the following messages are linked to the donor updates:
- InfectiousDiseaseMarkerResultRequest (IDM_RES)
- TypingResponseRequest (TYP_RES)
- NoResultRequest (NO_RES)
- ReservationResultRequest (RSV_RES
These 4 and newly 2 more (SMP_ARR and SMP_INFO) will be replaced with the Match-Connect API endpoints that have the donor details embedded in the message. Respective endpoints of IDM_RES and TYP_RES will deliver new IDM and new typing details, and all the mentioned endpoints will also inform the patient registry of the new donor status.
These donor updates are for the receiving registry (patient registry) only and will not be updated in the central HUB. So the sending (donor) registry is responsible to send a DIFF upload to the S&M system in parallel to keep information in sync.In the future a block for ADCUs may come to play.
| Donor type | Payload | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Adult donor |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CBU |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ADCU | In the future |
Here is the comparison of the DONOR_CB and the API endpoints: EMDIS vs API.xlsx
...
The WMDA will provide a standard response to request messages sent to MatchConnectMatch-Connect. It's Its structure is as follows:
| Field | Details |
|---|---|
| sender | string maximum: 9999 minimum: 0 maxLength: 4 minLength: 4 example: 5678 4 digit ION of sender |
| deliveredAtUtc | string($date-time) Server-supplied timestamp showing time of Message delivery to recipient's inbox queue |
| referenceMessageId | string($uuid) |
| responseType | stringEnum: Array [ 3 ] |
| wmdaRemark | [...] |
...