Skip to content
This repository has been archived by the owner on Aug 12, 2022. It is now read-only.
New issue

Patient Impact API

Past due by over 2 years 58% complete
  1. The API(s) collect the necessary events or status updates per patient (not summarized).
  2. Data collected from the API(s) must be sufficient for the Government to summarize impacted patient information by disaster, state, time frame, status, and facility, or a combination of these.
  3. The API(s) input must be compatible with patient, facility, and staff inform…
  1. The API(s) collect the necessary events or status updates per patient (not summarized).
  2. Data collected from the API(s) must be sufficient for the Government to summarize impacted patient information by disaster, state, time frame, status, and facility, or a combination of these.
  3. The API(s) input must be compatible with patient, facility, and staff information as provided in the Government GitHub repository.
  4. The API(s) allow updates to patient status due to a disaster. Available patient statuses include unaffected, injured, ill in facility, ill but not in facility, deceased, and isolated. For example, the API may inform the Government of different scenarios, such as:
  • As of January 3, 2022, patient ID100 is deceased as the result of a pandemic related incident that occurred at a particular facility in Texas.
  • As of 10/31/22, patient ID200 is injured but convalescing at home due to damage to a facility as a result of an earthquake.
  1. For the initial release of the API, assume facility systems have a hard-coded list of disasters.
  2. The API(s) need to be secure, and require authentication by the healthcare facility. For the purposes of this challenge, the vendor may choose an appropriate authentication/authorization solution for the problem. Please document the reason for the choice in the Decisions section of the Case Study. Facility systems can only update information for patients that relate to their facility (transferred into the facility, transferred away from facility, or currently at a facility and patient status requires a change).
  3. The system will support millions of patients and staff, and can anticipate occasional, sudden rapid updates when hospitals identify patients under disaster conditions and need to update patient status en masse.
Loading