-
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
Product realisation of MHR concept #131
Comments
Requires #132 to define device type. |
The only outstanding query is a type code for the Organisation Legal Entity (Australian Digital Health Agency). A request for advice has been sent to the ABS to provide advice on a relevant ANZSIC industry code for health agencies including Services Australia and Australian Digital Health Agency. This is not required to establish a functioning baseline so it will be split off and managed via a separate issue. |
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 Development and internal design architecture review is complete, internal unit testing is underway via AN-3, Clinical Informatics peer review is underway via AN-5, AN-6, AN-7, and AN-8. |
Definition of MHR concept is also part of the NCSR to MHR integration project. Development and internal design architecture review is complete, clinical Informatics peer review is underway via AN-24 and AN-23. This is a review activity to close off internal development against the existing requirements and design before putting this work on hold. The NCSR to MHR integration project has been de-prioritised by Dept of Health so this work will go on hold. A complete, correct draft set of materials is intended to be handed over to the project on completion of this review activity. Temporary branch for review: http://build.fhir.org/ig/AuDigitalHealth/ci-fhir-r4/branches/NCSRIntegrationDraft/ |
AN-23 and AN-24 in review with @dbojicic-agency. |
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. |
Product realisation of MHR concept as part of NCSR to MHR integration
MHR is a system device and operating organisation, that is a part of Australian Digital Health Agency.
Device:
Organisation Operator (national operator for MHR system):
Organisation Legal Entity (Australian Digital Health Agency)
Originally posted by @dtr-agency in #126 (comment)
The text was updated successfully, but these errors were encountered: