Tier 1 App Development Sandbox Status

Sandbox Guidelines for working with others...

Being considerate of other's data... Will it get cleaned up on a regular basis?

What about resource intensive operations? Are there limits? How to prevent them from impacting other consumers of the sandbox?

Can bring my own data? If so, can I wall it off?

Amy Ballard (Deactivated) to start the best practices guide for using the HSPC Tier 1 sandbox 12 Mar 2015

Organization	App Name	Description	Contact	Date Added
The Advisory Board Company	Crimson Care	Pull in patient clinical details from multiple EMRs when the Care manger is assigned to a patient and is reviewing their chart	Stacy Hawthorne	01/15/2015
Systems Made Simple	Enterprise Health Information Interoperability Platform (eHIIP)	A data aggregation platform that collects various forms of data (CDA, HL7 v2, FHIR, etc) from multiple sources and presents a unified, correlated and longitudinal record to a consumer.	Dan Ramunda	02/09/2015
Laconic Systems	ER Tracker	Digital ink enabled tablet PC app for clinician data entry tasks and document generation (PDF)	Chris Anderson	02/11/2015
Intermountain Healthcare	Bilirubin Chart	Patient Bilirubin count Threshold Viewer		02/01/2014
Intermountain Healthcare	ResearchDoc			05 Mar 2015
Arizona State University	AppWorks	Clinical Application Development Environment	Aziz Boxwala	12/15/2014
OSIA Medical	Asthma Ally/Health Ally	View chronic condition information (control test evaluations, self evaluations, trigger identifications, measurements, etc.) submitted by a patient via mobile device. Use prescription information aggregated across provider platforms to customize questionnaire delivered to patient via mobile device.	Rob Reynolds	01/15/2015

Resource	Read	Write	Update	Delete	Search Parameters	Query Notes
AdverseReaction	x	x	x	x	subject substance date	/wiki/spaces/HSPC/pages/14385187
Alert	x	x	x	x	subject	/wiki/spaces/HSPC/pages/14385192
Condition	x	x	x	x	subject encounter onset status [:text] code [:text]	/wiki/spaces/HSPC/pages/14385187
Encounter	x	x	x	x	subject status [:text] date	/wiki/spaces/HSPC/pages/14385198
FamilyHistory	x	x	x	x	subject	/wiki/spaces/HSPC/pages/14385201
Medication	x	x	x	x	code [:text]	/wiki/spaces/HSPC/pages/14385203
MedicationPrescription	x	x	x	x	patient encounter datewritten	/wiki/spaces/HSPC/pages/14385205
MedicationStatement	x	x	x	x	patient	/wiki/spaces/HSPC/pages/14385207
Observation	x	x	x	x	subject name [:text] date status [:text]	/wiki/spaces/HSPC/pages/9044000
Patient	x	x	x	x	name [:exact] family [:exact] given [:exact] gender [:text] birthdate active [:text]	/wiki/spaces/HSPC/pages/7274570
Practitioner	x	x	x	x	name [:exact]	/wiki/spaces/HSPC/pages/16285719
Substance	x	x	x	x	type [:text]	/wiki/spaces/HSPC/pages/14385209
AllergyIntolerance
CarePlan
Procedure
Questionnaire
RelatedPerson
Organization
MedicationDispense
Immunization
ImmunizationRecommendation
Device
Medication
MedicationAdministration
Location
Order
OrderResponse
List
Media
Other
Provenance
SecurityEvent
Binary
Composition
DocumentReference
DocumentManifest
DiagnosticReport
ImagingStudy
Supply
DeviceObservationReport
Conformance
Profile
ValueSet
ConceptMap

Parameter	Qualifiers	Notes
_sort	asc, desc	_sort is used to sort a result set on a specified parameter. Qualifiers asc and desc indicate ascending or descending. Ex. _sort:asc=name
_count	na	_count is used to specify the number of results to be returned to the client. The result set will contain links to allow the client to request subsequent pages.
page	na	page is used for paging through a result set. URLs containing the page parameter are returned by the server along with result sets. The client should not create URLs containing the page parameter.

Requirements for the FHIR data representation...

Amy Ballard (Deactivated) to build this out. 26 Feb 2015 HRI-338 - Getting issue details... STATUS