MIT-LCP / MIT-LCP/mimic-code

The data in the prescription table but not in the emar table, and the opposite case

Open
#1,185 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Jupyter Notebook
Stars
3.4k
Forks
1.7k
PR merge metrics
No merged PRs in 30d

Description

Prerequisites

Hi! First of all thank you for creating and maintaining this useful dataset.

As far as I know, prescription table and emar table can be linked to each other via 'pharmacy_id' columns.
And what I've tried is investigating the relationship b.w them using 'pharmacy_id' columns as a key.

I've wondered about

  1. the data in the prescription table but not in the emar table,
  2. and the opposite case (the data in the emar table but not in the prescription table,

In what situations does each type of data come from?

I guessed a few things.

for the first case,

If prescription can be cancelled after prescription is issued, then

for the second case,

There could be some drugs that can be administered to patients without corresponding prescriptions from doctor
Or emar can contain the drug administration data after the patient leave the hospital

Anyway, the reason is still unclear.

Maybe you can understand my question more easily with the code below I wrote .

image

Thank you!!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the MIMIC online documentation and the prescription and emar table definitions, focusing on how pharmacy_id is assigned and used. Compare the two cases described in the issue and document the situations that explain each mismatch; done means the relationship and exceptions are clearly documented.

Written by the indexing model from the issue text.

Assessment

Domain
data, databases
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.