You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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).
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.
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.
The text was updated successfully, but these errors were encountered: