Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

HAZARD: Unavailability of the dGC API calculation and charting functions #51

Open
pacharanero opened this issue Apr 27, 2021 · 1 comment
Open

HAZARD: Unavailability of the dGC API calculation and charting functions #51

pacharanero opened this issue Apr 27, 2021 · 1 comment
Assignees
@pacharanero
Labels
documentation hazard likelihood-low Could occur but in the great majority of occasions will not. risk-level-1-acceptable Acceptable, no further action required severity-minor Minor injury, short term recovery; minor psychological upset; inconvenience; negligible consequence.

Comments

@pacharanero
Copy link
Member

Description

If the API does not respond then centile measurements will be unavailable

Effect

No response from the API would mean no growth chart calculation values and no graphical growth charts

Hazard

In the absence of a measurement from the API, users may have to fall back on manual methods of centile calculation such as printed Growth Charts.

Harm

It is hard to envisage the unavailability of the API causing any form of harm to a patient because there are immediately available fallback methods such as manual calculation on printed paper charts.

Possible Causes

  1. Failure of internet connectivity at Site
  2. Failure of Internet connectivity at Supplier/Integrator
  3. Failure of Internet connectivity at Microsoft Azure UK Data Centre
  4. Failure of internal networking in Azure cloud platform
  5. Failure of proxying through Azure API Management Platform
  6. Failure of the API server WebApp platform
  7. Failure of the API server application code

Assignment: Assign this Hazard to its Owner. Default owner is the Clinical Safety Officer @pacharanero
Labelling: Add labels according to Severity. Likelihood and Risk Level
Project: Add to the Project 'Clinical Risk Management'
@pacharanero pacharanero added the new-hazard-for-triage A new hazard which needs to be triaged for severity and likelihood, scored and assigned. label Apr 27, 2021
@pacharanero pacharanero self-assigned this Apr 27, 2021
@pacharanero pacharanero added likelihood-low Could occur but in the great majority of occasions will not. risk-level-1-acceptable Acceptable, no further action required severity-minor Minor injury, short term recovery; minor psychological upset; inconvenience; negligible consequence. labels Apr 27, 2021
@pacharanero pacharanero transferred this issue from another repository Oct 24, 2022
@pacharanero pacharanero removed the new-hazard-for-triage A new hazard which needs to be triaged for severity and likelihood, scored and assigned. label Oct 24, 2022
@pacharanero pacharanero changed the title Unavailability of the dGC API calculation and charting functions HAZARD: Unavailability of the dGC API calculation and charting functions Oct 25, 2022
@github-actions
Copy link

Thank you for opening or editing a Hazard in the Hazard Log.

Next steps:

  • Please use the Labels feature in the right sidebar area to stratify this Hazard in terms of Likelihood and Severity
  • Assign the Issue to the Clinical Safety Officer for triage

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pacharanero pacharanero

Labels
documentation hazard likelihood-low Could occur but in the great majority of occasions will not. risk-level-1-acceptable Acceptable, no further action required severity-minor Minor injury, short term recovery; minor psychological upset; inconvenience; negligible consequence.
Projects
RCPCH Digital Growth Charts Hazard Log
Status: Mitigated
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pacharanero