-
Notifications
You must be signed in to change notification settings - Fork 3
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
StructureDefinition - Statement of Vaccination to support exchange of digital health in Australia #115
Comments
Confirmed with maintainer of HL7 AU Base to migrate the vaccine vial serial number extension into AU Base - pre-ballot as level 0 'potentially useful extension'. ADHA Core Immunization development complete and ready for assurance. |
May 2022 QA Preview - http://build.fhir.org/ig/AuDigitalHealth/ci-fhir-r4/branches/2022May/package.tgz The FHIR R4 conformance artefacts are a set of StructureDefinitions that define the FHIR structures required, the data element definitions, and their associated rules of usage including the use of extensions and terminology. These conformance artefacts will be published in an Agency FHIR NPM package for use with FHIR and FHIR-aware tools. The FHIR package contains the validation form (JSON + SCH) of the conformance artefacts for direct use in validation operations and example resource instances that demonstrate use cases and conformance requirements. While these artefacts and their package have been developed in conjunction with this Agency FHR implementation guide – publication and release of the implementation guide is not in scope. The implementation guide is provided to assist readers and users in understanding the Agency FHIR NPM package. See http://build.fhir.org/ig/AuDigitalHealth/ci-fhir-r4/branches/2022May/index.html |
Feedback raised during the assurance period from internal testing, CI SME design review, and NIO have been addressed. A new frozen QA Preview baseline is available. Changes from internal assurance between v1.0.0-qa-preview and v1.0.0-qa-preview2 :
ADHA profiles amended (changes listed above): June 2022 QA Preview - http://build.fhir.org/ig/AuDigitalHealth/ci-fhir-r4/branches/2022June/package.tgz The FHIR R4 conformance artefacts are a set of StructureDefinitions that define the FHIR structures required, the data element definitions, and their associated rules of usage including the use of extensions and terminology. These conformance artefacts will be published in an Agency FHIR NPM package for use with FHIR and FHIR-aware tools. The FHIR package contains the validation form (JSON + SCH) of the conformance artefacts for direct use in validation operations and example resource instances that demonstrate use cases and conformance requirements. While these artefacts and their package have been developed in conjunction with this Agency FHR implementation guide – publication and release of the implementation guide is not in scope. The implementation guide is provided to assist readers and users in understanding the Agency FHIR NPM package. See http://build.fhir.org/ig/AuDigitalHealth/ci-fhir-r4/branches/2022June/index.html Cycle 1 clinical Informatics peer review AN-8 complete with no changes required. Cycle 2 internal unit testing continues via AN-3. Cycle 2 clinical Informatics peer review continues via AN-5, AN-6, AN-7. |
The final baseline of the ADHA FHIR NPM package & IG is released for assurance as 1.0.0-qa-preview3. This version reflects final design agreements with NIO and Oracle and addresses feedback raised during the assurance period. http://build.fhir.org/ig/AuDigitalHealth/ci-fhir-r4/branches/2022Aug/package.tgz Changes from internal assurance between v1.0.0-qa-preview2 and v1.0.0-qa-preview3:
ADHA profiles removed as part descoping ExplanationOfBenefit.referral:
This version is undergoing internal release readiness and regression testing via AN-477, and publication readiness review via AN-431, Agency Governance review via Collaborate. |
Prerequisites
The issue / feature
Change description
Design and develop a set of materials that define a Clinical Information Object for Vaccination for the electronic exchange of vaccination and immunisation information between patients, healthcare providers, and between healthcare providers and the My Health Record system infrastructure in Australia.
What are the use cases we want to support?
TBD
What it actually enables people to do
Mockups
If applicable, add screenshots or mockups to help explain the issue / feature.
How awesome would it be?
TBD
Workarounds
TBD
Additional context
As part of the development of this profile we need to ensure:
The text was updated successfully, but these errors were encountered: