For our health plan partner, we came up with an executive dashboard to facilitate monthly and ad-hoc status reports based on several iterations. As the dashboard components and the data elements became better understood and well-defined, sections of the report became automated over time.
For example, we can easily track and develop reports around registration including tie-backs to the registration source including affiliates who may be issued custom keytags to identify where members came from:
We can also measure progress toward profiling our members and share this information with the community:
The federal agency who provided the financial support required quarterly, bi-annual and annual reports. These structured report formats were based on old models of telehealth which assumed patients were visiting clinics. This difference between the Network design (free-living patients interacting via mobile devices, email and web) and the more traditional office-centric view of healthcare presented challenges which required education and the creation of entirely new metrics. For example, the less we know about a member the more our metrics resemble advanced web analytics representing unique visitors, messaging traffic, content testing, etc... For some portions of the reporting I used Google Analytics while others were developed using a mash-up of Google Docs spreadsheets and proprietary mobile gateway reports.
For consumers we needed to provide custom feedback. One example of this has become somewhat industry standard in today's world of cloud-based diabetes software systems. I call it the Day Over Day report and it displays time series data in a format that is easy for anyone to understand including an easy format for both patients and their physicians to discuss. I imagine we will design a series of similar report formats that facilitate collaboration amongst the many stakeholders in the region.
