-
Notifications
You must be signed in to change notification settings - Fork 1
Home
Tom Schenk Jr edited this page Jan 3, 2018
·
5 revisions
| Work / Scope | API Deliverable | Model | ETL | Runner | ORA Wrapper |
|---|---|---|---|---|---|
| INTERNAL TESTING | v0.3.0 | ||||
| ADJUST API NAMING CONVENTIONS | v0.4.0 | ||||
| Since the API will be used for more than just Alliance, adjust naming conventions to ensure a more consistent roll-out of the API across agencies. Tweak internal scripts and also the API documentation to reflect these changes. Conduct smoke testing to ensure everything is functional and commit/push all code changes to the repos. | |||||
| ROBUST ERROR HANDLING | v0.5.0 | v1.0.0-rc.1 | v1.0.0-rc.1 | v0.9.0 | |
| Add robust error messages to clearly communicate any errors, issues, or if data is not yet available. All errors should be returned through HTTP Status Codes communicated in the API. | |||||
| RISK SCORE | v0.6.0 | v1.0.0-rc.1 | v1.0.0-rc.1 | v1.0.0-rc.1 | |
| Add messages and notes for the risk scores being returned through the API to describe the risk level for the child and remediation or referral suggestions. | |||||
| IMPLEMENT SECURITY TOKEN | v1.0.0-rc1 | v1.0.0-rc.1 | v1.0.0-rc.1 | v1.0.0-rc.1 | v1.0.0-rc.1 |
| This will implement a mandatory security token which must be passed to the API before a result will be passed back to the hospital. For each transaction, the security token and timestamp for each transaction must be logged. Smoke testing should be conducted. | |||||
| TESTING | v1.0.0 | v1.0.0 | v1.0.0 | v1.0.0 | v1.0.0 |
| Conduct load and soak testing to ensure the API and surrounding infrastructure can tolerate high and sustained demands from the API that are outside normal expectations. All testing to this point has been basic “smoke” testing. |