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.

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

[NEW STANDARD] - The Standards must outline an exceptions process for handling non-conformance and resolution pathway #144

Open
10 tasks
ChrisSquats opened this issue Apr 18, 2024 · 0 comments · May be fixed by #181
Assignees

Comments

@ChrisSquats
Copy link
Collaborator

ChrisSquats commented Apr 18, 2024

Summary

Many incumbent systems do not meet the API standards. We need to detail the process for non-conformance.

Suggestions

  • A register of services and their conformance is maintained
  • For non-conformant services, include a list of standards that aren't met
  • List any compensating controls
  • Outline a path to resolution
  • Define a grace period of non-conformance. Proposal is for 24 months to accommodate large changes in architecture that may be required to achieve conformance.

Drawbacks

None identified

Which area of the standards does this apply to?

  • Part A - API Concepts
  • Part B - API Security
  • Part C - API Design and Development
  • Part D - FHIR
  • Community guidelines
@ChrisSquats ChrisSquats linked a pull request Jun 21, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant