NHS31xx SW API
tadherence: Therapy Adherence Demo Application

Detailed Description

The Therapy Adherence Demo application will demonstrate the value proposition around therapy adherence use case. This application together with a smart blister or a demo PCB and an Android application will serve as a starting point for app developers to develop a full blown solution helping patients adhering better to their therapy.

Introduction
This demo application is designed to run on an NHS31xx IC mounted on an Demo PCB or Demo foil. Depending on the sensing principle the correct NHS family member should be chosen. Please refer to Specific part for the Sensing Component to understand the sensing principles available for your NHS IC.
In the ARM application, regardless of the sensing principle, the present pills are divided into groups, these groups are defined by the drive pin of a certain subset of the pills.
ARM application overview
The aim of the ARM application is to (once the therapy is started), keep track of pill removals. Therefore the chip will be periodically woken up to update its therapy status (re-check the pill precedence). For every removal, an event is stored in non-volatile memory such that, later, a host device (smartphone) can read these via NFC. Most of the UI is done over NFC (NDEFT2T) using a complementary android application.
The following user actions may be triggered via NFC (using a dedicated smartphone app.):
  • Start a new therapy
  • Configure the therapy
  • Stop an ongoing therapy
  • Reset the "smart-blister"
  • Read out the therapy adherence (how many/which pills were/weren't taken)
Besides this way of interaction (via dedicated smartphone app.), basic therapy status will be exposed via standard NDEF TXT records which can be read out and displayed by any NFC capable smartphone, thus, without the need of a dedicated app. In a reduced top level view, this application is formed by the main application file and several SW components which, in turn, rely on underlying infrastructure drivers and middleware modules (see respective component documentation): The top level flow of the application is described in the following diagram:
dot_inline_dotgraph_2.png

The top level design of the application is clarified in the following block diagram:

dot_inline_dotgraph_3.png

Modules

 Memory Manager
 
 Message Handler Module
 
 Text Component
 
 Therapy Component