Apr 22nd, 2009, 11:29 AM
Hi Alex,
Thanks for the post!
The API actually doesn't have functions for retrieving the raw submission data yet (but it will!), but you can always require() the /global/library.php file and use the core's ft_get_submission_info function - that does what you need. You can find it in /global/code/submissions.php.
But instead, couldn't you do this? (I'm not 100% sure if it fits your needs):
1. create client accounts for each of the wards.
2. create a separate View for each ward. Each View would limit the results to only show submissions within that particular ward. (As such, you will need a "ward" field to be added to your forms in case they don't already have it).
3. Assign each ward to a particular View.
With this in place, they can then log in and update their patient information without seeing any other patients in any other ward.
Would that work, do you think?
- Ben
Thanks for the post!
The API actually doesn't have functions for retrieving the raw submission data yet (but it will!), but you can always require() the /global/library.php file and use the core's ft_get_submission_info function - that does what you need. You can find it in /global/code/submissions.php.
But instead, couldn't you do this? (I'm not 100% sure if it fits your needs):
1. create client accounts for each of the wards.
2. create a separate View for each ward. Each View would limit the results to only show submissions within that particular ward. (As such, you will need a "ward" field to be added to your forms in case they don't already have it).
3. Assign each ward to a particular View.
With this in place, they can then log in and update their patient information without seeing any other patients in any other ward.
Would that work, do you think?
- Ben