Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

READY TO CONFIG GAP

LOW MEDIUM HIGH

CES = Companeros En Salud

Notes: All tickets should be labelled "PIH" and "PIH-CES"

Questions:

  • Localization of labels (e.g. being able to toggle from Spanish to English for volunteers who don't speak local language) - support in AMRS forms?
  • Call w/ Brandon +/- Mike
  • Try to implement whole form


About CES EMR

Also moving to cloud connection to local office server (currently doing database merging manually). (Local cloud datawarehouse)

If this + 3.x goes well, this becomes the dream site for PIH. 

Functionality in PIH Mexico (CES):

Theme

Feature

StatusPriorityNotes/Comments

Registration

Address Hierarchy (certain fields required) - go from country down (See how Bahmni does their Hierarchy too)





GAP

3 LOW

Update

Ticket:

Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.

RegistrationAdd Relationships

READY

4 READY


Registration

Many obs needed (e.g. Religion, Marital Status)

GAP

3 LOW

Need ability to add obs to the Registration form. 

Q: Should we make the whole Reg form just a form, configurable via Form Builder, that's no longer hard coded?

A: Would need a lot of additional work done to Ampath Forms. 
Registration

Contact Person (not a patient in the EMR)

GAP

1 HIGH

Would be "To Config" as long as there's Obs group support

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

RegistrationPersist birthdate-estimated

READY



Registrationmonths estimated


GAP


3 LOW
(Registration not in scope for CES Patient Chart pilot)
Registration

Ability to hide drop down if only one option or default

GAP

3 LOW

(Registration not in scope for CES Patient Chart pilot)
RegistrationPrint ID Cards

GAP

3 LOW

ID cards not used at CES)

(Registration not in scope for CES Patient Chart pilot)

Registration

Warning for registering patient very similar to another existing patient

GAP

3 LOW

(Registration not in scope for CES Patient Chart pilot)
Clerk Dashboard

Search for a patient is built-in to register workflow (prevent accidental duplication)

GAP

3 LOW

(Registration not in scope for CES Patient Chart pilot)


This didn't always help prevent duplicated data entry at CES in the past anyway, though it would be good to have eventually.

Clerk DashboardWorkflow for Registration clerk after Registration (e.g. take to patient Reg Dashboard or a list of recently registered patients)

TO CONFIG

3 LOW

Configurable: Just make Submit Button redirect configurable. (Super easy if not configurable already - ticket: ____ (low complextiy) Grace Potma 

Clerk Dashboard

All non-clinical info

GAP

3 LOW

Way to edit individual patient details (e.g. no pencil in Details expander) - ticket: ___Grace Potma 

Patient SearchSearch for patients alive or dead

GAP

HIGH

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Search currently does not return any dead patients (even if searching by ID) 

Visit Management

Auto-clean up of active visits

Happens on Server

READY

4 READY

Each distro has task that runs on each server that looks for visits to close. (e.g. If 12+hrs without activity, visit is closed as of the last activity.)
Visit Management

Ability to edit visit dates

Need to be able to remove End Date and extend the visit if patient accidentally got automatically ended when the patient in reality was actually admitted

E.g. click here to edit this active visit: e.g. to say this actually ended at this date at this time (but we accidentally left it open)

GAP

3 LOW

Active Visit button could link to Encounters space - then in encounters widget you could edit current or past encounters - ticket: ____ Grace Potma 

Visit ManagementUI prevents starting another visit if there's already an active visit

GAP

3 LOW

Need both UI and actual blockage of having multiple active visits at once. 

(Current error message not reliable)

Visit ManagementCheck: How are vitals slotted into present visit? (Happening as expected?) What about edits to Care Programs, Meds, Conditions etc - is this logged against that visit? Or the encounter? Or...?

DEV CHECK

1 HIGH

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

VitalsVitals form/entry

GAP

1 HIGH

Currently not configurable. Configure to add things like Glucose etc

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

VitalsToggle between Pediatric and Adult Vitals forms

GAP

3 MEDIUM


Patient Clinical Summary/Dashboard

Recent Visits

Allergies

Relationships (broken down between Healthcare Providers and other relationships)

programs

patient attachments/documents

READY


4 READY



Patient Clinical Summary/Dashboardobs graphs

GAP

3 MEDIUM


Patient Clinical Summary/Dashboardrecent obs

GAP

3 MEDIUM


Start Visit/Add Past visit


READY

4 READY


Consult Note

Display past vitals in note



GAP

3 LOW

Not necessary in 3.0 as users can view vital more easily anyway
Consult NoteMany Obs (free text, radio buttons, dropdowns)

READY

4 READY


Consult Note

Diagnosis entry widget

agement:

Auto-suggest:

Action of changing between Primary vs Secondary; First Time; Confirmed vs Suspected

GAP

2 MEDIUM

Does AMPATH forms support a dx widget?
Consult Noteskip logic

READY

4 READY


Consult Note

Med orders

GAP

1 HIGH

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Need to be able to configure fields on order so that fewer fields are included/required.

Consult Note

print prescriptions

GAP

1 HIGH

Unable to locate Jira server for this macro. It may be due to Application Link configuration.


Program enrollmentEnrollment via pt chart

READY

4 READY

via Program enrollment widget
Program enrollmentautomatically based on certain answers in a form ("enroll in program" tag - when you submit the form, pt is enrolled in that program. Tag has option to display checkbox, so they'll only enroll the pt if that checkbox is checked)

GAP

3 LOW

Need to confirm program enrollment UI desired by CES team

Though, CES did this because wasn't happy

Program enrollmentautomatically based on completion of a certain form

3 LOW


Program enrollmentcan't fill out a certain form unless already enrolled in related program

GAP

1 HIGH

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

paper record management

not live yet (schedule?)

  • Informs user about where the paper record is (e.g. id of the paper record - may be multiple ids per patient because they many have different types of paper records in different documents)
  • Sign out the paper record

GAP

5 NA

not live yet (schedule?)

merge visits


GAP

3 LOW

Need legacy UI module to be able to get into 2.x patient view and do this thing
Legacy functionalityNeed a way to link to legacy functions we may not be building in 3.0 initially.  (merge patients, make patient deceased etc...)

GAP

1 HIGH

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

merge patients

Merge patients

GAP

4 READY

Again, should be able to link to legacy version of this from 3.0 

mark patient deceased

Access through General Actions:

 

GAP

3 LOW

Use Legacy UI?
mark patient deceased

OR in consult note; mark disposition as "Death"

GAP

3 LOW

not needed for CES
mark patient deceased

OR when you complete a program enrollment: 

GAP

3 LOW

not needed for CES
mark patient deceased

Tag in Header for "Deceased"

GAP

1HIGH

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Link to Jira Issues for Gaps

type key summary assignee reporter priority status resolution created updated due

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  • No labels