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
Hi @sesola - do you mind providing the copy we need to use on the website please? The most important thing for example is what term we use to refer to the records (as from user testing it seemed 'medical records' is confusing) and the clear warnings we provide before the user goes ahead and sends PDF files.
And then add the required copy you actually want as comments. To do this you press the comment icon on the top header and then select wherever you want to add a comment. If you don't have a comment there we will assume you're happy with the copy.
Let me know if any issues!
The text was updated successfully, but these errors were encountered:
''Medical information extracted are immediately pseudo-anonymised and then encrypted before analyses''
''Medical professionals must only used this app on a secure or trust-approved computer. The uploaded files(s) will be stored locally but wiped when you close the app.
'' This current software iteration is only optimised for scientific and research purposes. It must not serve as aid in clinical decision making.''
Hi @sesola - do you mind providing the copy we need to use on the website please? The most important thing for example is what term we use to refer to the records (as from user testing it seemed 'medical records' is confusing) and the clear warnings we provide before the user goes ahead and sends PDF files.
The simplest way to do this is if you could go to the wireframes here (on the desk version): https://www.figma.com/file/BaIHfKxJN8zhXlVoTxlTJu7B/CURENETICS2?node-id=47%3A1181
And then add the required copy you actually want as comments. To do this you press the comment icon on the top header and then select wherever you want to add a comment. If you don't have a comment there we will assume you're happy with the copy.
Let me know if any issues!
The text was updated successfully, but these errors were encountered: