appertafoundation / diadem Goto Github PK

Any area of the app or website asking for feedback should point to the User Voice page until all integration is completed https://community.apperta.org/forums/601567-diadem

date of birth - should this be mandatory? I skipped this and it worked
need a way of confirming date of birth so no automatic move on

Add PostCode to 'Location' screen + amend data posted to demographics service

• Website

The DiADeM resources will be published on the following websites:
YHSCN.nhs.uk, Code for health, DiADeM website, Apperta.org, Applicationinsight.com, Alzheimer’s Society, Skills for Care, Dementia Partnerships

• Emails

An email describing the new app will be sent to:
Yorkshire and Humber Regional Dementia, Commissioning Leads, CCG GP Dementia Leads, Old Age Psychiatrist Group, Memory service network, Fiona Macmillan to forward to Skills for Care contacts, David Evans [email protected] to send to, CHAIN network, Clinical Networks across the country (Alistair Burns group), YH CN Dementia E Bulletin

• Twitter

A series of 140 character tweets will be generated and tweeted from the following accounts:
@YHSCN_MHDN, @NHS_YHSCN, @code4health, @DiADeM_App, @Apperta, @app_insight, Alzheimer’s society, @SkillsforCare

• TweetDeck

Set up a series of timed tweets from the above acco

• E - Bulletin
  The YH CN will promote DiADeM in their September, October, November and December bulletin. This will go out on the first Thursday of every month using the following text:
  NEW DiADEM app launched!

Diagnosing Advanced Dementia Mandate (DiADeM) is a protocol that was developed approx. 2 years ago and is used across the Yorkshire and the Humber region in a paper based format. In partnership with Code4Health the paper based tool has been converted to an award winning* app and can be downloaded here .
Having the app installed on a mobile device will:

· Reduce the time needed to forward think to download the paper based tool, print and take with in advance of a care home visit
·  Remove the need the for manual calculation, reducing user error
·  Communicate the result safely and securely to the patients GP
·  Improve access to post diagnostic support.

A diagnosis of dementia is usually made within memory services. Some care home residents with advanced dementia have never had a formal diagnosis. In these cases a referral to memory services is rarely desirable and likely to be distressing for the individual. In these cases, the DiADeM app can be used to inform a diagnosis decision. Click on this link for more information.

***Winner of 2017 Northern Lights Quality Improvement Awards.

• Webinar

The YH CN will host and record a webinar to introduce and demonstrate the use of DiADeM. This will be recorded and hosted on our website as a longstanding resource.

• Events

The following events organised by the CN will provide an opportunity to promote the app.
• 6th September CCG GP Leads meeting
• 12th September joint Memory Services/RDL’s meeting
• 18th October Dying Well

• External Meetings
  ·        7th September Partners in Care (care homes York)
  ·      11th September NIHR MH and Dementia research meeting
  ·      8/9th November Dementia Congress

• Strategy group meetings
  Include DiADeM update at the Dementia Strategy group updates
  The following events organised by the CN will provide an opportunity to promote the app.
  • Regional dementia leads meeting
  • Memory service network
  • Acute dementia champions

• Case studies… (website)
  Buckinghamshire case study
  Croydon
  Wakefield

• Early Adopters of DiADeM App
  York
  Wakefield

• set up basic encrypted save of composition data
• set up local manifest system for encrypted files
• set up system to manage retrieval and loading of encrypted files
• set up GUI to choose & load encrypted files

Scenario one- had GPCOG 0-4 so does not need to go to
informant page- informant only required if score 5 and above

• complete the 'message' GUI module
• extract context specfic text from the existing 'manual' document
• update context specific text for each screen in the app
• create a local store for this text (in a form that can be updated easily)
• create a system of extracting relevant content for each screen
• create 'calling' GUI in the app (i.e. a "I" button)

App screen doesn't realign with the ipad screen i.e.
doesn't turn through 90 degrees when you rotate the IPad

• get UserVoice credentials & learn how it works
• populate UserVoice with content from Colin's user manuals
• set up connection between the app and UserVoice
• arrange local storage of UserVoice content & system for synching
• adapt gui used for previous context-sensitive help for use with UserVoice content

• set up encrypted storage of login credentials
• set up GUI informing user when connection is not available and a choice to proceed or not
• set up and/or modify existing GUI for offline usage (i.e. for ehrid, NHS Choices)
• link in with the encrypted storage feature at #27

• test connection to the existing demographic service
• set up calling scripts in DiADeM & Test OpenEHR
• add new functions to libEHR code library
• create new GUI to access the service
• date-of-birth value must be mandatory and should not have a default value

• liaise with Dave Jobling about creating '[email protected]
• liaise with Dave Jobling about setting up dns records for this email
• amend code on diademauth.code4health.org to use this new email
• test with multiple email recipients

Instead of sorting out the domain and emailing directly from the server the new approach is to make API calls to an external email messaging service - see #106

It may be good to add in that a Dementia Assessment was done 'code' when a DiA DeM
assessment has been done even if it does not indicate Dementia

we need to bring all the good content over to UserVoice (an incorporate that nicely into the
app too) - move to new requirement this is not linked to title above

displays incorrect username or password

The logical way to go through the DiADeM tool is from 1 to 5. However, in the App version the pathway goes 2 first then 1,3,4,5. Are we able to bring the two in line so its much less confusing?
Options

1. Functional Impairment appears as the first 'criteria' in the App
2. Change Functional Impairment to no. 2 and Cognitive Impairment to no. 1 in the paper version and the App.

• reject non-nhs.net email adresses for DiADeM Recipient roles at diademauth.code4health.org
• improve the rejection message a user sees when attempting to use a non-nhs.net email

At this point, all reports generated by Diadem contain patient identifiable data. So sending reports from Diadem should be restricted to nhs.net email domain only

When a request is made to send an assessment as a pdf report via email as described in #15 , the requester should receive a confirmation email once the report has been sent.

• consider changing 6 CIT question 5 to use the same marking as GP COG question 6

If a user has previously tapped the switch to agree to the Terms and Conditions, it should be able to remember this for the next time he or she is at the login screen and have the switch already tapped indicating that the Terms and Conditions have been already agreed to

@applicationinsight to provide me or @david-jobling the links to the various stores in order to create the download buttons.

Describe different approaches taken for 'preferences' data as well as part-completed or completed data* collected during a DiADeM session with a patient (that would be posted to OpenEHR as a composition)

• = potentially 'patient identifiable data'

Login free text box to have labels

1. Email address
2. Password

• implement custom popups for iPads and desktop versions
• modularise the custom popups used in several places in Test OpenEHR
• integrate with DiAdeM GUI (to appear in iPad and desktop versions)

http://diadem.apperta.org/ to be the Main Hub for ALL DiADeM functions including

• Home - General information pages
• About DiADeM
• User Voice pages
• Registering for an account
• Log in and Manage account

• liaise with NHS Choices about how to find robust data sets
• incorporate a 'fetching' module in DiADeM
• create new GUI (including reducing list of choices from search parameters)

On notification that Operon's N3 is working:

• test basic connection from app to web service and on to N3
• amend DiADeM & Test OpenEHR calling scripts as necessary
• amend libEHR code library as necessary

• complete the DiADeM data flow scenarios - taking into account such changes as JWT

in several other screens a 'Next' button appearing when the user has completed an action has been seen as useful - if it's useful in those screens it will be useful in the new 'Choose Recipients' screen

When a user tries to send a report, the server sends back a notification about the status of the request. If report generation fails (due to server issues, or because user provided an non-nhs email), it should be possible for app to display a failure notice to the user

Diadem server should maintain a list of 'pre-approved, verified and safe' email recipients. It should only be possible for users to send reports to an email address in this 'safe list'.

This issue is linked to @ColinSloane's comment in issue #54

The app does not open on some/many Android devices

The issue is the LiveCode built-in encrypt (and decrypt) functions fail, and these are called during the app's instantiation.

For the moment, to allow for testing the rest of the app on Android, build 0.9.8.2 on Android does not use encryption. To get this temporary build ensure the "WHAT'S NEW" section of the listing on Google Play reads "This build manages a bug in how encryption is handled in Android"

• bad date formatting from date picker in the 'Patient' screen
• unable to query the demographics service due to bad date format
• date picker sometimes appears already open when entering the 'Patient' screen
• a selected date appears with the year in two digit form (i.e. "03")
• revisiting a previously populated date picker shows the date beginning with "20"
• the 'firstName' field & associated assets in the 'Patient' screen sometimes are not visible after ending an edit
• the 'Login' button in the 'Login' screen sometimes remains 'greyed-out' when it should be blue (although it still does work)
• 'flash' of input fields on leaving some screens
• 'flash' of input fields on closing the slide-up menu
• on returning to the app, if a partly-completed diadem session was left from the previous session the app returns to the same screen (i.e. it does not force the user to login again) - perhaps the solution is to offer to save progress up to the current screen and then kick the user out so they have to login again and then choose the partly-completed composition (if they wish)

make sure the app elegantly manages the situation where they have saved their 'favourite' DiADeM Recipient in the app, but since they last used the app the recipient's organisation name or email address has been changed on the server

• get UserVoice credentials and learn how it works
• set up 'receiving' forum/threads/compartments at UserVoice
• set up connection between the app and UserVoice
• set up 'posting' code to send reports to UserVoice
• create a GUI for the use to report issues

Agree. This can be included in the body of the email. Or we can do it server side. Probably easier to include in body of email via app.

Diadem app should be able to request assessments to be sent as pdf reports attached to email. It should be possible to send emails to one or more recipients.

In the reports where dementia is not indicated, I would suggest changing the wording from:
"There is no need to add this patient to the GP Register using the ICD 10 code(s)."
to
"There is no need to add this patient to your GP practice dementia register."

In the reports where dementia IS indicated, we're using the wrong coding terminology - it's not ICD10 codes that will be used (they're used in hospitals), it's CTV3/Read Codes:

"Please add this patient to the GP Register using the ICD 10 code(s) taken from the North Guidance on Dementia and Delirium Coding document published July 2014." I think we also need to change, "Or using the regionally, locally agreed ICD 10 codes in your area please also consider adding other codes highlighted in the report which help to indicate location of patient and blood test declined."
to:
"Using the appropriate QOF codes please record whether the appropriate blood tests -
routine haematology, biochemistry tests (including electrolytes, calcium, glucose, and renal and liver function), thyroid function tests, serum vitamin B12 and folate levels - have been carried out or record where these blood tests have been declined or excepted." (Need to check this wording with Sara)

Also suggest changing the next paragraph to: "Ensure that planned follow-up and next steps are recorded in the patient's health record including any
onward referrals where appropriate. Ensure that arrangements are made with the patient
and carer (where applicable) to jointly review the care plan."

• create a sized range of PNG images of logo
• import font used in logo text
• incorporate these assets in the splash screen and the app
• create LiveCode-readable SVG colour images of logo
• create LiveCode-readable SVB colour images of logo text
• incorporate these assets in the splash screen and the app

Choose recipient- if not there, can it be skipped? I had to select one of the recipients to get to next page. Can you skip if you don't want to upload to recipient?

Jay to write a statement and produce a flow chart to demonstrate thr safe storage of patient identifiable information

Is there a reason why DiADeM is asking to access local files?