Closed dtr-agency closed 2 years ago
The following diagram describes the expected relationships to the national cancer screening program participation record in the Agency's Clinical Information Architecture.
No expected future overlap with existing document types - other NCSR information, if supported, would overlap with records including referrals, reports, claims.
The core concept of a national cancer screening program record will be defined as a superclass of the agreement of a common definition for information exchange that can be:
The requirements for support at completion of this release are:
Future specialisation may be defined for a particular domain, reporting requirements, historical or some other requirement.
At this time all elements are common to each program.
To support this release, and to underpin all disease screening program participation records the following concept architectures will be defined as per the concept hierarchy above:
The Agency Clinical Information Architecture approach of Clinical Information Objects will define additional component Clinical Information Object architectures.
To support key strategic objectives in Australia in support of digital health and interoperable data standards developed in collaboration with our partners this work will produce:
National data model for health program participation information in development as Health Program Participation Observation. ADHA specialisation for NCSR to MHR in development as ADHA National Cancer Screening Program Participation Observation ADHA view support in development as ADHA National Cancer Screening Program Participation Composition
Information about participation in a health program is a summary observation with component observations.
Solution options proposed in early design workshop 27/01/202: Observation, Procedure, Extension (complex), Encounter-grouped, Composition-grouped, List-grouped. Follow-up design workshop 01/02/22 to walkthrough solution options selected Observation to pursue.
The scenarios below are only for high-level design activities - they do not represent implementation, validation, persistence or processing decisions. The scenarios do demonstrate the data scenarios documented below and the record categorisation and metadata design documented in Typing, subtyping and categorising national cancer screening program participation records #129.
NCSR receives cervical result (NCSP Data Scenario 1: Active screening, next action in 1 year) and FOBT for patient (NBCSP Data Scenario 3: Active screening, next due in 2 years) on 22 May 2021. Participation information is updated in the NCSR for both NCSP and NBCSP and sent to MHR system 22 May 2021. Sample instance:
The MHR system generates and persists: the Payload Bundle, a National Bowel Cancer Screening Program Participation Record DocumentReference and Observation, a National Cervical Cancer Screening Program Participation Record DocumentReference and Observation, and may persist the authoring information (Device & Organization). Sample instances:
DocumentReference for National Bowel Cancer Screening Program Participation Record
DocumentReference for National Cervical Cancer Screening Program Participation Record.
Patient is now eligible and due (NBCSP Scenario 1: New to Screening). Participation information is updated in the NCSR for NBCSP and sent to MHR system 05 February 2022. Sample instance:
The MHR system generates and persists: the Payload Bundle, a National Bowel Cancer Screening Program Participation Record DocumentReference and Observation, and may persist the authoring information (Device & Organization). Sample instance:
DocumentReference for National Bowel Cancer Screening Program Participation Record
A Clinical Information System views the Patient's program participation information held in the MHR system on 06 February 2022. Sample instance:
A Clinical Information System views the patient's NCSR program participation information held in the MHR system on 15 February 2022 - the MHR system has generated a National Cancer Screening Program View on demand (Document Bundle), that contains the retrieved Observations and Organization (NCSR Operator), and includes generated Composition, Patient, Device (MHR), and Organization (MHR Operator) according to business rules. Sample instance
Continuation of scenario 2.... NCSR recieves information that patient has opted to defer (NBCSP Scenario 2: New to Screening, Deferred) 15 May 2022. Participation information is updated in the NCSR for NBCSP and sent to MHR system 15 May 2022. Sample instance:
The MHR system generates and persists: the Payload Bundle, a National Bowel Cancer Screening Program Participation Record DocumentReference and Observation, and may persist the authoring information (Device & Organization). Sample instance:
DocumentReference for National Bowel Cancer Screening Program Participation Record
A Clinical Information System views the Patient's program participation information held in the MHR system on 16 May 2022. Sample instance:
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/
Clinical Informatics peer review and limited testing complete via AN-24 and AN-23:
Other changes introduced via whole-sale enhancement to StructureDefinitions:
The NCSR to MHR Integration FHIR payload materials have completed development of this material including HL7 AU Base content, SNOMED CT-AU content, clinical Informatics peer review and limited testing, FHIR Architecture review, and Terminology review.
This work is now on hold until progressed as part of a work program.
Product realisation of NCSR concept (as part of integration with MHR) #130 remains open until the infrastructure identifiers for the NCSR (PAI-D, PAI-O, etc.) are registered.
Prerequisites
The feature
Design and develop a set of materials that define the payload for sharing of program participation information from the National Cancer Screening Register (NCSR) for the electronic exchange of national cancer screening program participation information between patients, healthcare providers, and between healthcare providers and the My Health Record system infrastructure in Australia.
Coverage will be provided for all programs currently supported by the NCSR: the National Bowel Cancer Screening Program (NBCSP) and the National Cervical Screening Program (NCSP).
This work will focus on:
The conceptual architecture will define support for:
The implementation architecture for the first release will support a FHIR R4 payload and retrieval of a generated narrative-only CDA payload that allows for:
Potential future work may include support for:
What it actually enables people to do
The My Health Record system has been identified as a key integration systems that can promote program uptake through better interaction between Healthcare providers and eligible Healthcare recipients.
The NCSR-MHR integration will encourage conversations about program participation status during a usual healthcare provider and consumer encounters. By providing visibility of program participation status in the National Consumer Portal (NCP), National Provider Portal (NPP), clinical information system (CIS), and hospital system like HIPS we can encourage these conversations, assisting in uptake of the screening programs and improved health outcomes.
How awesome would it be?
Excellent - work program requirement.
Workarounds
N/A
Additional context
There is no current support in MHR for:
The set of records associated with a national cancer screening program include:
The NCSR integration project will introduce the capability to share with the MHR:
Architecturally relevant business drivers: