View source for Igor Sirkovich, 2008 Care Transfer Request

Comment during PC WGM 17 sept Q3: " this might be handled as a "tracking the request".

Action plan is: 
1. Isobel Frean will submit a summary on this from here PhD
2. We will check back with Ontario on it and see if it meets the use case requirement
3. A description will be made in HL7 PC format
4. Modellers will look at dynamics and statics of it.
Perhaps there is need for both a tracking R-MIM and IN
and for a eligibility checking mechanism R-MIM and IN.

William

-
----


Hello,

We have a requirement for a receiver of a Care Transfer Request to send an "in process" status to notify the sender that they have started working on the verification of the patient's eligibility. Once the eligibility is verified, a receiver will send a Care Transfer Promise or Reject. We suggest to use a Verification Observation to communicate the "in process" status with either ActStatus=active (verification is been performed) or ObservationValue=INPNDINV (inactive - pending investigation). But we are not sure which interaction to use. Care Transfer Request and Notify Care Transfer Request are sent by the sender, not by the receiver of a referral. Sending Promise with a verification observation and then another Promise or Reject when an eligibility is verified, doesn't look well. We will appreciate your advice.

Thanks,

Igor Sirkovich
Information Architect, HL7 & Integration
Continuing Care e-Health Ontario, Standards Team

Hi Igor,

You wouldn't use either of those interactions (Care Transfer Request or Notify care Transfer Request) as you have indicated.

Also, since the status of "In Process" will typically be conveyed back to the 'Placer' of the transfer request any time after a promise has been issued to fulfill the request, this calls for a new interaction where:
    Trigger Event --> Notify Care Transfer "In Process" Status
    Sender  --------> Care Transfer Fulfiller
    Receiver -------> Care Transfer Placer
    Message Type ---> Care Transfer Status (new message type with limited attribution)

Essentially, this is analogous to the 'Notify Care Transfer Promise'
interaction (REPC_IN003010UV), but with different TE and MT.

I hope that helps.

Regards,

John Kufuor-Boakye

Hello,

As we see no objections to John's suggestion, we are planning to go ahead with a new "Notify a Status of the Care Transfer Request" interaction and "Care Transfer Status" message type as an extension to the Care Transfer Topic. Once we finish modeling, we will submit this to the Patient Care for inclusion in the Care Provision Domain Ballot.

Thanks,
Igor Sirkovich