1 / 55

Project

Project. PROMETHEUS Software for Stem Cells Donor Registries. EMDIS messages. Mechelen, Belgium February 2013. Content. Physical and logical message D ONOR_ CB message categories Log. message folder Log. message status New and old log. message Relations among log. Messages

Télécharger la présentation

Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Project PROMETHEUS Software for Stem Cells Donor Registries EMDIS messages Mechelen, BelgiumFebruary 2013

  2. Content • Physical and logical message • DONOR_CB message categories • Log. message folder • Log. message status • New and old log. message • Relations among log. Messages • Demonstrations

  3. Physical and Logical messages • Physical message – it concerns EMDIS system data message. For example: • Message of the type TYP_REQ is a physical message • Message of the type DONOR_CB is a physical message (one donor in a search result) • Logical message – the logical messages concern us rather more than physical messages i.e. in the way how an user comprehend them. A logical message is a group of physical messages. An user always works with logical messages. However, the physical messages are sent to abroad for example. • Search result is a logical message which can contain tens of physical messages of the type DONOR_CB but also others (PHEN_LIST, MATCH_SUM) • Typing request is a logical message which contains only one physical messages of the type TYP_REQ.

  4. Donor_CB The DONOR_CB arriving physical message is assigned to the logical message category according to these criteria: • If the donor status is RS (reserved for our patient) => the resulting category is "Donor status RS" • If the donor status is TU (temporarily unavailable), OP (reserved for other patient) or DE (donor is deleted) and we had sent the request before => the resulting category is "Donor status change" (negative answer to our request) • Concerning the patient with who we have already worked (i.e. some our request has been already created) => the resulting category is "Key donor update" • Concerning the answer to our Preliminary request or Patient update => the resulting category is "Search result" • Concerning the group of donors containing the donor who is Available and his HLA match grade is 6/6 Allele Matched, 6/6 Potential (Allele) Matched or 6/6 Antigen Match (Allele Mismatch) => the resulting category is "Search result upd.(!)" (i.e. important search result update) • Other cases => the resulting category is "Search result upd." (less important search result update)

  5. Status of EMDIS messages • Prepared to send – log. message prepared to be sent but it is not actually sent so processed by the ESTER system. • Sent – sent log. message. • Received – received log. message. • Prep.to send,canc. – log. message prepared to send which was canceled before sending by an user. • Sent,cancelled – sent log. message which was canceled after sending by an user. • Received,cancelled – received log. message later canceled by a sender. • Received,not proc. – received search request for which the ESTER system hasn't done a search yet. That's a temporary state that will change to Received after doing the search. • Received,denied – received log. message which was by some formal reason denied, e.g. breaking the EMDIS rules.

  6. New and Old EMDIS Messages • New – every recently received or every recently sent message. • Old – every message which was marked as already processed by an user. And administrative messages that would otherwise clutter EMDIS NEW.

  7. Requests and results • List of requests without result • Links between messages Donor is reserved Typing request Typing result Preliminary request Search result Sample request Sample arrival date Warning Sample result

  8. EMDIS Items of a Donor • Donor status, HLA • Ethnic – the ethnicity of the donor, an optional item • Donor CMV status - an optional item • Date of CMV test - an optional item • Toxoplasmosis - an optional item • EBV status - an optional item • Donor collection type • Number of PBSC • Number of MARROW • Number of pregnancies - thenumber of pregnancies of the female donor, an optional item • Number of blood transfusions - the number of blood transfusions, an optional item • Donor height - the height of the donor, an optional item • Donor weight - the weight of the donor, an optional item

  9. EMDIS Items of CBU's • Collected net volume of CBU • Volume of frozen CBU • Collected net number of nucleated cells • Number of nucleated cells in frozen CBU • Collected number of CD34+ cells • Number of CD34+ cells in frozen CBU • Collected number of mononucleated cells • CFU preserved • Method of volume reduction • CBU CT typing date • CBU DNA available • Maternal serum available for CBU • Quantity of maternal serum for CBU

  10. Basic work with EMDIS • Patient EMDIS Tools • New EMDIS messages • Old EMDIS messages • EMDIS requests without result (New and Old)

  11. EMDIS Messages (EMDIS - new) Double Click

  12. EMDIS Old

  13. Emdis Message

  14. Donor's EMDIS messages

  15. EMDIS communication rules • EMDIS Documentation • Prometheus Documentation • Patient side and donor side • BE SOP's and Manual

  16. Preliminary Request and Patient Update

  17. Change Patient Status

  18. Alternative Match List Requests • Simple mechanism to obtain mismatched donors for a patient. • Provides cord blood units with up to two major antigen mismatches (as usual) with regards to the phenotype given. • The alternative phenotype does not go into the repeat search process.

  19. Typing Request

  20. Sample Request

  21. IDM Request Not used very often Registries send IDM results to CT requests as policy

  22. Donor Reservation Request Not Frequently Used – Registries reserve donors as policy Requires a Reservation Result

  23. Cancellation of a Request Note: different behaviour with a “Prepared to send” and a “Sent”message

  24. CBU report request • No EMDIS supported format of CBU report • Request contain Email and FAX details • Request contains preferred result method

  25. Internal EMDIS requests and results System allows to create these internal EMDIS messages: • Preliminary request • Patient update • Change patient status • Search result • Search result upd. • Typing request • Result of typing • Sample request • Sample arrival date • Sample testing result • IDM request • Result of IDM req • No result • Donor status change

  26. Internal EMDIS requests and results System does not allow to create these internal EMDIS messages: • Alternative phenot. - specialsearchstrategy in local databaseisdone by internalsearchtool • Donor reserv. request - reservation of local donor for local patient is done in evidence of donors • Donor reserv. result - reservation of local donor for local patient is done in evidence of donors

  27. Message Reports (Print)– 1st Method

  28. Message Reports (Print)– 2nd Method

  29. Automated Processing Messages automatically processed by the system: • Preliminary Requests → Search results • ALM requests → Search results • Patient Status change → Status changed → Donor updates etc.

  30. Typing Request

  31. Typing Result

  32. Typing Result Update Donor with Typing Results Don't forget to validate donor Go to original Typing Request → Send results

  33. Typing Result

  34. Typing Result Nothing to fill in → Data comes from the updated Donor Record Once processed don't forget to tick OK on both Request and Result to send the to EMDIS old

  35. Sample Request

  36. Sample Result Establish Availability of the Donor Determine Sample Arrival date Create Sample arrival date message

  37. Sample Arrival Date

  38. Sample Arrival Date

  39. IDM Report – to a Sample Request

  40. IDM Request

  41. IDM Result Update Donor Record Result data is taken from Donor Record

  42. IDM Result Update Donor Record Result data is taken from Donor Record

  43. Donor Reservation Request

  44. Donor Reservation Result

  45. CBU Report Request Establish preferred method of the recipient for delivery of the CBU report

  46. Text Message

  47. Text Message form Text messages may be sent between HUBs in conjunction with patient cases. Text messages can also be directly linked to a previous message or Request

  48. No Result When for reason of the donor the service cannot be done: Send a No Result message

  49. No Result

  50. Message Denial

More Related