-
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
Define donation decision and consent from Australian Organ Donor Register #141
Comments
ADHA Extension Date of Initial Registration refactored for R4 ceb1dff |
Consent scope needs to be defined (mandatory) - existing values in core FHIR may not be suitable for organ donation. Query if ADR is suitable or if an additional concept should be defined. There isn't anything suitable in SNOMED CT for consent scope, propose addition to HL7 AU if needed. Upon consultation, the use of adr is appropriate in R4 - the code is deprecated. Note in current draft of R5 scope is no longer present in the resource. |
Removed donationdecision extension that is no longer required in R4 due to resource restructure Restructured to handle multiple provisions Added examples for 2 additional use cases aodr-2 (donate all) and (aodr-03) donate specific tissue or organ #141
CodeSystem: Consent Scope Codes included in the HL7 Terminology package is missing the concept 'adr' 'Advance Care Directive' as published in the ValueSet Consent Scope Codes bound in Consent. See Zulip Consent Scope Codes stream and HL7 JIRA UP-255. |
source value was wrong so invariants weren't being rendered #141
Issue in supporting transition between the CDA or RIM format and the FHIR format (both STU3 and R4) of an Australian Organ Donor Register form. The terminology that represents organ or tissue for donation doesn't have a defined transition from the NCTIS terminology supported in the original CDA (RIM) format and the SNOMED CT terminology supported in the FHIR format. The CDA format supports the legacy value set NCTIS Organ Donation Consent Provision Type that uses concepts from NCTIS Data Components code system. The FHIR format supports the value set Organ Donation Body Site that uses concepts from SNOMED CT. Concept maps are required to define to define that transition but are not yet available. |
FHIR Architecture Review Outcomes on AODR set of profiles
Changes from FHIR Architecture Review complete. |
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. |
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 2 internal unit testing continues via AN-3. Cycle 2 clinical Informatics peer review continues via AN-5. |
Cycle 2 clinical Informatics peer review AN-5 complete with no changes required. |
Review and testing for this profile is complete. Next step is to mark as Active v1.0.0 and pass regression testing. |
NIO have advised Date of initial registration not provided in live feed - removed from Medicare Records FHIR IG via AuDigitalHealth/ci-medicare-records#23. NIO have advised this data is present in 2018 and earlier content ingested via CDA. Need to retain this extension to support existing data. This extension may be refactored to have a correct R4 URL as the original STU3 extension was never implemented. |
This extension was refactored to have a correct R4 URL as the original STU3 extension was never implemented. #141
This extension was refactored to have a correct R4 URL as the original STU3 extension was never implemented. #141
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. |
Merge in CIL/ci-fhir-r4 from CIFMM-4068-profile-element-out-of-order-schema-errors to master * commit 'c3375065a89a2958d30a3fc75f496d077237431f': Fix out of order StructureDefinition elements
Prerequisites
The issue / feature
Change description
Develop and publish an payload definition for R4 of donation decision and consent from Australian Organ Donor Register to provide an initial baseline as input a the piece of work to provide FHIR R4 endpoint for the exchange of digital health information recorded on the Australian Organ Donor Register between individuals, healthcare providers, and the My Health Record system infrastructure in Australia..
What it actually enables people to do
How awesome would it be?
Support transition from STU3 to R4 of digital health exchanges of an individual's information in relation to the Medicare program.
Workarounds
N/A
Additional context
Current implementation defined by:
The text was updated successfully, but these errors were encountered: