Requirements
- The main goal of this project is to provide medical professionals with a tool to allow secure and robust transfer of communication (text, images, videos, audio) between healthcare professionals.
- simplifying and securing messaging between healthcare professionals
- User Interface
- Easy to use
- Visually appealing
- Messaging
- Read messages (text)
- Read sent messages (text)
- Send messages (text)
- Receive files (images, videos, audio)
- Download sent files (images, videos, audio)
- Send files (images, videos, audio)
- Messages should have a doctor, patient, subject and priority fields
- Message search
- Message sort
- Message forwarding
- Message reply
- Delete messages(just on sender’s phone)
- Prioritize messages (red=urgent, green=unimportant, etc..)
- Sending message unknown contact throws a warning requiring confirmation
- Contacts
- Add contacts
- Remove contacts
- Maintain contact list (on or off the device)
- Contact search (existing)
- Contact search (new contact based on profile settings)
- Settings/Profile
- Only authorised users can use the application
- Create an account
- Enter name
- Enter email
- Enter phone number
- Hospital
- Set/change password
- Password recovery
- Profile picture
- Delete account
- Auto delete messages after <time period> (sent and received)
Nice to haves
- Video conferencing
- Group chat
- Patient subscription (possibly hospital/dept subscription)
- Auto messages delete (you can only read a message once)
- Patient identification via wrist band image
- Read receipt (Notify sender when the message has been read)
- Drafts
Constraints
- must follow certain health care protocols and distribution of private patient information (Healthcare Canada and HSSBC Approval)
- Users must be doctors (later on maybe nurses and some others)
- Secure
- user authentication
- data transfer must use acceptable encryption
- log in/log out
- auto logout on loss of network connectivity
- login timeout (logout on app losing focus)
- more investigation needs to be conducted to find what is sufficient
- If we develop an app it needs to be easily accessible (unclear how to do this)
- If we develop a web page it needs to be compatible with firefox and chrome
Team,
This is a great first step, well organized and thought out. Good talking to you again this morning.
Whether to go for a dedicated app (iOS, android) or a web / email-based approach I will leave up to you, but my preference would be to do whatever would be the best user experience and then concentrate on one platform – I would prefer to see a slick, working prototype on one platform than a half baked effort on multiple.
My bias is iOS as I and most clinicians that I know use iOS, but probably a good idea to do what is best in terms of your collective expertise. Having said that, it might be an opportunity to learn something new, ie coding for iOS which might come in useful going forward as a new skill acquired. As I said, I could probably provide an old iphone. Web based might be the best compromise.
Under ‘create account, I would add: ‘CPSBC ID number’ as a way of identification. Not sure if we’ll be able to use it or not…
Under ‘nice to haves’, I’d also add in OCR so that by pointing the camera at the pts label, or a screen etc, it can get their name, DOB, MRN etc with an option of saving it under a pt list and include biometrics for login (thinking iphone fingerprint).
Looking forward to the proposal and next meeting.