Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Medical History Report] Insufficient detail to merge encounters #107

Open
EasternPA opened this issue Mar 16, 2023 · 2 comments
Open

[Medical History Report] Insufficient detail to merge encounters #107

EasternPA opened this issue Mar 16, 2023 · 2 comments

Comments

@EasternPA
Copy link

I see numerous encounters in the UNASSIGNED section of the Medical History Report that lose fidelity when I try to merge them with conditions. I can't match these up. I don't want to open them in this screenshot for privacy reasons, but they need details, such as the medication name.

missing detail

@EasternPA
Copy link
Author

EasternPA commented Mar 17, 2023

I was able to match many of these manually. By viewing the details of any single medication listed on an UNASSIGNED visit (see #103 ), I memorized the first few digits of the "Id" field of a medication request JSON. Then I went into the report editor and opened all the Encounters shown above until I found the one with a medication entry with the Id that matched what I memorized from the Medical History view.

If you pull the medication name over in addition to the unique id of the specific request, that would go a long way toward helping us pair up unassigned encounters with a condition. I'm still left with a couple of dozen entries that show a date and facility name but nothing else and no detailed view. The other half of the picture I attached to #101 shows only the facility name and nothing else (which is why I didn't include it).

@EasternPA
Copy link
Author

I was mistaken. I see now that you can click on the date of an Unassigned Encounter to view the detail. The mouse pointer remains a vertical bar for non-clickable text, but it is a hyperlink to the detailed JSON behind the Encounter. That helps whittle down the list of Unassigned Encounters that this issue is referring to overall.

@AnalogJ AnalogJ added this to the v1.0.0 Release milestone Oct 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

2 participants