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

(chore) set restrictByVisitLocationTag parameter to true #869

Merged
merged 1 commit into from
Nov 22, 2024

Conversation

mogoodrich
Copy link
Member

@mogoodrich mogoodrich commented Nov 22, 2024

This will update the Reference Application to use the newly-implemented functionality to restrict visits to those tagged as visit locations (and to default the visit location to the "nearest" visit location associated with the session location), following the O2 Ref App model.

@ibacher ibacher merged commit f2a62c5 into main Nov 22, 2024
13 checks passed
@mogoodrich
Copy link
Member Author

Thanks @ibacher , I confirmed that this is place and seems to be working (after a ctrl-reload).

@gracepotma lmk if you have any questions around this, but, basically, when starting a visit you can now only choose a location that is tagged as a "Visit Location". In most cases (like with all the "Site x" locations) the locations have been tagged as both Visit and Login locations so you won't see much change. What is different is for the 5 locations that I've made children of "Ubuntu Hospital" (Inpatient Ward, Outpatient Ward, Wards 1, 2 & 3) you won't be able to choose them as visit locations, and if you are logged into those locations and try to start a visit, the default visit location is set to "Ubuntu Hospital" (representing the fact that your overall visit is at Ubuntu Hospital, though you may have encounters at various different locations within it).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants