Issues

Some sandboxes have resources that have been deleted in the history table, but are not deleted in the primary table.
HRI-695
A user validates a Stu3 resource instance using a profile with the $validate operation (support Stu3)
HRI-694
A user validates an STU3 resource instance using the validate operation with the profile parameter (see 7.5.4 Asking a FHIR Server)
HRI-693
DSTU2 api calling infinite number of times for Observation resources when there are many resources tied to a patient (100s)
HRI-692
Look into SMART bulk data specification
HRI-691
Posting a bundle to the HSPC v5 reference-api will fail, throwing an exception
HRI-690
Part 2 - A user of the Reference API uses the $validate operation to validate a FHIR resource according to an US Core profile
HRI-689
Update the HPSC EC2 launch configuration to pull ecs.config from S3 (support for docker authentication)
HRI-688
Reference auth does not seem to support CORS at the /token endpoint (specifically for getting a refresh token)
HRI-687
Part 1 - A user of the Reference API uses the $validate operation to validate a FHIR resource according to an FPAR profile
HRI-686
A user of the Reference API creates their own FHIR Resource that
HRI-685
Part 2 - (4) Talk with Kevin and Zach about what session context a CDS Hooks sandbox user would like passed from the HSPC Sandbox to the Hooks Sandbox
HRI-684
Part 2 - When a user creates a DSTU2 sandbox with default data, they see a launch scenario for Bilirubin and CDS Hooks (also make one for Bilirubin Risk Chart)
HRI-683
Stale search results for the reference api are not being cleaned up
HRI-682
The HAPI 3.0 library sends search results to the wrong connect (default)
HRI-681
When a user creates an account using Google, they are not redirected to the sandbox manager after account creation.
HRI-680
A user of the Reference API loads the FPAR (OPA) structure definitions
HRI-679
(DSTU2) A user of the Reference API is able to use the HAPI CLI to load the Argonaut profiles
HRI-678
(DSTU2) A user of the Reference API is able to use the HAPI CLI to load the Snomed terminology packages required by the Argonaut profiles
HRI-676
A user of the Reference API loads the terminology to validate FPAR profiles (patched)
HRI-675
(DSTU2) A user of the Reference API is able to use the HAPI CLI to load the Loinc terminology packages required by the Argonaut profiles
HRI-674
(Strategy) A reference api user is able to migrate their sandbox to a newer schema version
HRI-673
A user of the Reference API is able to use the HAPI CLI to load the Snomed terminology packages required by the HL7 FHIR DSTU3 base profiles)
HRI-672
The sandbox-manager app is deployed to hspc-test and available at https://sandbox-test.hspconsortium.org
HRI-671
The patient-picker app is deployed to hspc-test and available at https://patient-data-manager-test.hspconsortium.org
HRI-670
1-25 of 325