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
With 2.x we have clearly seperated the ideas of registering and looking up patients within the system. This issue is to track the development of tracking patients returning to the hospital through a 'Visit' entity.
The following features must be designed and implemented for the core featureset:
Final database design for what is required to be tracked in a 'visit'
Client UI module in the 'Patient Record' page to allow checking in
Server API for checking in and reviewing patient visists
We should also be researching what comprises a visit:
What implications does a patient visit have financially?
What kind of reports do we need to see for patients, what information is needed to drive these reports?
The text was updated successfully, but these errors were encountered:
@jniles Ah I did not see that this issue was being tracked, I notice that you are assigned. Is this feature partly developed or have you not begun on this yet? If it has not been started I could tackle this as a ui-router nested view proof of concept.
No, I was planning on beginning it, but Patient Invoice refactor took much longer than expected. Feel free to start work on it! I've unassigned myself.
With 2.x we have clearly seperated the ideas of registering and looking up patients within the system. This issue is to track the development of tracking patients returning to the hospital through a 'Visit' entity.
The following features must be designed and implemented for the core featureset:
We should also be researching what comprises a visit:
The text was updated successfully, but these errors were encountered: