Versions Compared

Old Version 130

changes.mady.by.user Matt Prestegaard

Saved on

compared with

New Version 131

changes.mady.by.user Matt Prestegaard

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This message is used to request an extended typing of a donor (adult, adcu, cbu?). It will primarily contain information about what to type and for which donor.
Added to that a patient block (ref?) containing up-to-date information about the patient, and an address block (ref?) containing up-to-date contact-information about the needed institution(s). 
Expected return message is 'typing result' (5.2) or 'request rejected' (5.14).
Check paragraph '5.18 Extended Typing' for the related message flow.

SendRetrieve
TypingRequestRequestTypingRequestRetrieve
Expand
titleRequest...
FieldDetails
request
Expand
title...
FieldDetails
requestDate*string($date-time)

Request date REQ_DATE Req 8 yyyy-MM-dd [or yyyyMMdd]

resolutionRequired*string
maxLength: 11
minLength: 11
example: HHHHMMM-H-H

Character string with fixed length in which each position represents a HLA locus. The coding of the resolution required for every position is: S = serological L = DNA low resolution M = DNA medium resolution H = DNA high resolution - (hyphen) = not requested The character string is interpreted from left to right, with position 1 as the leftmost position. The positions for the HLA loci are defined as: Position 1: HLA-A Position 2: HLA-B Position 3: HLA-C Position 4: HLA-DRB1 Position 5: HLA-DRB3 Position 6: HLA-DRB4 Position 7: HLA-DRB5 Position 8: HLA-DQA1 Position 9: HLA-DQB1 Position 10: HLA-DPA1 Position 11: HLA-DPB1

urgent*boolean

Urgent request URGENT Opt 1

remarkstring
maxLength: 120
nullable: true
example: patient case is very urgent

Remark REMARK Opt 120

addressEmbedded Address Block
recipientinteger
maximum: 9999
minimum: 0
maxLength: 4
minLength: 4
example: 1234

4 digit ION of recipient

patientEmbedded Patient Block
donorEmbedded Donor Block
Expand
titleResponse...
FieldDetails
wmdaResponse{...}
Expand
titleRequest...
No parameters specified
Expand
titleResponse...
FieldDetails
originalMessage{...}
metaInformationEmbedded Meta Block

Rules

Examples for field resolutionRequired:

...

SendRetrieve
TypingResponseRequestTypingResponseRetrieve
Expand
titleRequest...
Field

Details

response
Expand
title...
FieldDetails
referenceCodestring($uuid)
hlaNomenclatureVersionstring
default: 3

Major version of HLA Nomenclature HLA_NOM_VER Req 7

etSampleTypestring
nullable: true

Type of sample. AS = CBU Contiguous Attached Segment WB = Whole Blood Sample RC = Red Cell Fraction (pellet) FP = Blood Spotted Filter Paper ED = Extracted DNA

Enum:
Array [ 5 ]
remarkstring
maxLength: 120
nullable: true
example: patient case is very urgent

Remark REMARK Opt 120

recipientinteger
maximum: 9999
minimum: 0
maxLength: 4
minLength: 4
example: 1234

4 digit ION of recipient

donorEmbedded Donor Block
patientEmbedded Patient Block
Expand
titleResponse...
FieldDetails
wmdaResponse{...}
Expand
titleRequest...
No parameters specified
Expand
titleResponse...
originalMessage{...}
metaInformationEmbedded Meta Block
  • Extended Typing Result
    • patient (wmdaId)
    • referenceCode 
    • hlaNomenclatureVersion
    • etSampleType
    • remark
  • Donor Block (6.1.4)
  • Meta Block (6.1.1)
    • Payload TypingResponse

    Rules

    After the TypingResults (TYP_RES) message which includes an embedded donor (DONOR_CB) block, a separate update must be made to the Search & Match system with the updated donor data to ensure up-to-date master data.  More information on how to do so may be found here.

    ...