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

The non-conformance process #181

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

The non-conformance process #181

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b943c10
initial commit of the non-conformance process
ChrisSquats Jun 21, 2024
d13fef8
tidy up wording
ChrisSquats Jun 21, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions docs/api-concepts/05-Non-conformance.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
---
title: Non-Conformance
---

The API Standards are set at the standard the health sector should be operating at. However, due to the reality of the environment, there is a known deficiency in some of the existing products and services. The approach of these API standards is to keep them at the higher level and document the non-conformance and path to conformance.

## Non-comformance process

Non-conformance **MUST** be documented for API Consumers and API Producers of the Digital Services Hub where applicable.

Digital Services Hub maintains a register of non-conformance.

The registers includes:
- A list of standards that aren't met
- Any compensating controls
- Outline a path to resolution

The grace period of non-conformance is 24 months from entering the register. This is to accommodate large changes that may be required to achieve conformance e.g. architecture, or technology changes.