The purpose of the HSPC sandboxes is to provide HSPC application developers a running version of a certified HSPC platform to test their work against and platform integrators a set of HSPC certified applications to test their platform against. A common challenge faced by most clinical application developers is access to a realistic set of clinical data to test their applications against. Besides providing a production quality instance of a certified platform, the sandboxes will provide an extensive set of realistic (de-identified) clinical data available for testing applications as a preproduction step.
Current Sandboxes
In order for application developers to focus on development of application business logic, user interface concerns etc. without the need to worry about authorization, we expose an unsecured or "open" RESTful services endpoint:
HSPC Sandbox Open RESTful API Server: http://hspc.isalusconsulting.com/open-hsp-api. Click here for a listing of Patient resources in the sandbox against our Open RESTful API.
Once application development progresses to the point where it makes sense to introduce authorization, you can develop against our authorization server and secured RESTful API:
HSPC Sandbox Authorization Server: https://hspc.isalusconsulting.com/openid-connect-server-webapp
HSPC Sandbox Secured RESTful API Server: https://hspc.isalusconsulting.com/hsp-api.
Live Reference Implementation
Currently, there is a demo version of the latest "in development" version of the platform running here: https://hspc.isalusconsulting.com. The demo system can be used to test application integration with OAuth2, OpenID, and a small collection of FHIR data services that have been deployed. The data set is extremely limited at the moment and therefor the system does not provide a very useful sandbox. Developers are encouraged to download the reference implementation themselves and run it locally. See HSPC Developer Resources for instruction on how to download, configure, and run the reference implementation.