Cross-Population

[michaeledwardmarks]

When patient enters the OPAT Referral List ( #189 )

Cross-populate their data with existing data if they are a current inpatient

?One off at the time of adding patient as first iteration (this makes the OPAT episode actually separate from the Inpatient episode) ?Ongoing updating - this makes the Referral episode linked to the current inpatient episode

[GabPoll]

i can see the issue here, because it's all really one spectrum, but prefer if it's a separate episode. In that way it aligns with coding, clinic appts, etc... but also these patients get re-admitted often (ortho / vascular pts especially), and then it would make it difficult to track their next admission, if the OPAT clinic appt was no different to their last inpatient stay.

[davidmiller]

My current thought is that while there is a concurrent inpatient && OPAT episode, antimicrobials, investigations, diagnosis cross-populate bi-directionally.

OPAT/Inpatient episodes will be separate entities from the POV of data extraction &tc.

[GabPoll]

Umm... an interesting conundrum - does this mean we'll end up with overlapping episodes? I.e. Inpatient admission say 10/4/2014 - 18/4/2014. OPAT episode may start on 16/4/14 and then end 6 weeks later. But for period where the 2 overlap, then there is cross-population of antimicrobials, investigations and diagnoses? This is a nice solution if technically do-able.

Where would the clinical advice given be filed under. To go back to dates above, this patient may have initially come into contact with the Division of Infection on 14/4/14 via a conversation with micro (tagged micro on elCID), then 2 days later, they are accepted to OPAT and tagged as such, and perhaps the micro tag is dropped. However, I think that the OPAT episode of clinical advice should include the micro discussion, so that this is visible during future clinic appointments. What do you think @jonnylambourne ?

[davidmiller]

For #181 we introduced a hard-coded team population - e.g. when an OPAT episode is created, the patient must be in the referral list.

This is in opal/.../controllers/add_episode.js

Implementing this ticket should remove the need for that to be hard-coded into an OPAL controller.

[davidmiller]

This is now deployed to elcid-opat.

To use:

• locate a patient with an active inpatient episode.
• Make sure they have e.g. diagnosis/antimicrobials
• remember their hospital number
• go to the opat referrals list
• add a patient
• click "import from inpatient" button
• There is no step 7

We're not going to continue to x-populate for concurrent episodes for now I think - that's v. much a 2.0 feature :)

[michaeledwardmarks]

SO SEXY!