Skip to content

Update immunisation-history.yaml #195

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

Open
nkinsler1 wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Update immunisation-history.yaml #195

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a13e347
Update immunisation-history.yaml
nkinsler1 Oct 3, 2023
3634256
Merge branch 'master' into Update-row-47-49
helen-brown Feb 5, 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
4 changes: 2 additions & 2 deletions specification/immunisation-history.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,9 +44,9 @@ info:

The `COVID-19` data store is limited to vaccinations from England, Wales and The Isle of Man for the last 4 years. It has been approved to be used for clinical use cases.

The `FLU` data store is not yet populated and is planned to contain vaccination events captured through a point of care system in England for the last year. It has been approved to be used for clinical use cases.
The `FLU` data store contains vaccination events captured through point of care systems in England for the last year. It has been approved to be used for clinical use cases.

The `HPV` data store is not yet populated and is planned to be limited at first with vaccinations captured by the NHAIS system and in England only. It has been approved for use in clinical use cases.
The `HPV` data store contains vaccinations captured by the NHAIS system and in England only. It is not approved for use in clinical use cases.

## Who can use this API
This API can only be used where there is a legal basis to do so. Make sure you have a valid use case before you go too far with your development.
Expand Down