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?
Who's using the sandbox?
| 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 hawthors@advisory.com | 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, 703.289.5888 x7136 daniel.ramunda@systemsmadesimple.com | 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 | |||
| Arizona State University | AppWorks | Clinical Application Development Environment | Aziz Boxwala aziz.boxwala@meliorix.com 617-294-9269 | 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 rob.reynolds@osiamedical.com 801.230.6517 | 01/15/2015 |
- Scot Post van der Burg (Unlicensed) to build this out.
Sandbox Capabilities
Supported Resources
| 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 |
| 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] | |
| 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 |
Supported General Query Parameters
| 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. |
- Amy Ballard (Deactivated) to build this out (see the HiMSS data requirements spreadsheet) HRI-337 - Getting issue details... STATUS
Data Acquisition
Data Set Requirements
Requirements for the FHIR data representation...
- Amy Ballard (Deactivated) to build this out. HRI-338 - Getting issue details... STATUS
State of Data in Sandbox
- Scot Post van der Burg (Unlicensed) to load SMART data set this by
Resource | Simple/Example Test Data | SMART Data Set | Generated Data | De-identified Data | Data Mother |
|---|---|---|---|---|---|
| AdverseReaction | 18 on 10 Patients | ||||
| AllergyIntolerance | 18 on 10 Patients | ||||
| Alert | |||||
| Condition | 558 on 55 Patients | ||||
| Encounter | 1079 on 47 Patients | ||||
| FamilyHistory | 16 on 6 Patients | ||||
| Medication | |||||
| MedicationPrescription | 352 on 41 Patients | ||||
| MedicationStatement | |||||
| Observation | Bilirubin, Height, Weight | ||||
| 6 Patients | 64 Patients | ||||
| Practitioner | |||||
| Substance | 18 on 10 Patients |