-
Notifications
You must be signed in to change notification settings - Fork 17
DSU Getting Started Guide
Generally, there are two cases involved in getting started with a DSU.
- You have an app or device that communicates with an existing back-end server.
- You are building a new app or device or your app or device does not communicate with a back-end server.
If your application has a back-end where it stores data, turning it into an Open mHealth DSU takes a few steps.
- Add support for OAuth2.
- This will allow data from your application to be made available to other Open mHealth and OAuth2 systems.
- Implement the Registry API.
- Define Concordia schemas for each of your data payloads.
- Define a schema ID and version for each payload.
- The number and complexity of your data payloads determines the time it will take to create schemas on your data.
- If you already return JSON or XML for reads of your data, you have a good start.
- Implement the Read API.
- Based on your registry entries, allow data to be read from your system as a JSON array of data points.
- Implement the Write API. [Optional]
- When you are ready to publish your DSU, add the appropriate entries to the global Open mHealth registry by emailing [email protected].
- If you have visualizations or algorithms that you want to share with the community, get started with Data Visualization Units (DVUs) and Data Processing Units (DPUs).
For a new system, you can check out our reference implementation in this repository. A getting started guide can be found at DSU Reference Implementation: Getting Started.
The development process for a new system is similar to that of an existing system (see above), but you get to either build from scratch using existing implementations and this documentation as a guide.
The work effort is defined by programming proficiency and the number of data streams defined by your system. You can write a DSU in any programming language.
For more details about DSUs, check out the overview and the detailed documentation.
For questions, check out our discussion group.