...
Patients who have a PV record from Any Sending Facility which is enabled and no PKB membership. (
Status |
---|
colour | RedYellow |
---|
title | TODOSTARTED |
---|
|
(GS: How does this work with UKRDC Feeds? we currently don't have a way for this to work with UKRDC feeds unless the units send a PKB membership when they enable them for PKB)
Status |
---|
colour | RedYellow |
---|
title | TODOSTARTED |
---|
|
One record per UKRDCID.
Status |
---|
colour | RedYellow |
---|
title | TODOSTARTED |
---|
|
Output
PKB ProgramMembership Record, sent to UKRDC UKRDC
Status |
---|
colour | RedYellow |
---|
title | TODOSTARTED |
---|
|
-
https://jira.ukrdc.org/browse/PKB-106A28 Demographic Message (no ZTM Segment) sent to PKB PKB
Status |
---|
colour | RedYellow |
---|
title | TODOSTARTED |
---|
|
-
https://jira.ukrdc.org/browse/PKB-107Method
UKRDC Process va Mirth Mirth
Status |
---|
colour | RedYellow |
---|
title | TODOSTARTED |
---|
|
-
https://jira.ukrdc.org/browse/PKB-108 ,
https://jira.ukrdc.org/browse/PKB-109...
Patients who have a newly created PKB membership perhaps triggered as part of the PKB creation.
Status |
---|
colour | RedYellow |
---|
title | TODOSTARTED |
---|
|
Who have received PV XML File for the first time (GS: How does this work with UKRDC Feeds currently can only work if the feed includes a PKB membership indicator/new membership flag in some way)
Status |
---|
colour | RedYellow |
---|
title | TODOSTARTED |
---|
|
SendingExtracts HSMIG/PVMIG/PV/UKRDC are acceptable (though we don't expect there to be any HSMIG/PVMIG data for patients in this category). The only data sent should be from "Live" facilities.
Status |
---|
colour | RedYellow |
---|
title | TODOSTARTED |
---|
|
Output
This should be full PV Dump Dump
Status |
---|
colour | RedYellow |
---|
title | TODOSTARTED |
---|
|
Only those Message Types requested by the Unit, sent to PKB. -https://jira.ukrdc.org/browse/PKB-99
...
UKRDC Process via Mirth. The "Identify" code for this should be a separate channel to "New Patient Demographic Send" to separate counts however the destinations etc. can be shared.
Status |
---|
colour | RedYellow |
---|
title | TODOSTARTED |
---|
|
New Death Demographic Notifications
...
Patients who have an open PKB Membership.
Status |
---|
colour | RedYellow |
---|
title | TODOSTARTED |
---|
|
Who have an updated TRACING record containing a DeathTime which occurred more than two weeks ago.
Status |
---|
colour | RedYellow |
---|
title | TODOSTARTED |
---|
|
One record per UKRDCID UKRDCID
Status |
---|
colour | RedYellow |
---|
title | TODOSTARTED |
---|
|
Output
PKB ProgramMembership Record - with an End Date, sent to UKRDC.
Status |
---|
colour | RedYellow |
---|
title | TODOSTARTED |
---|
|
-
https://jira.ukrdc.org/browse/PKB-111A28 Demographic Message (no ZTM Segment) sent to PKB PKB
Status |
---|
colour | RedYellow |
---|
title | TODOSTARTED |
---|
|
- This is handled by
https://jira.ukrdc.org/browse/PKB-107 which will include the DOD in the PID segment if present. The logic needs to be amended in
https://jira.ukrdc.org/browse/PKB-112 though.
Method
UKRDC Process via Mirth Mirth
Status |
---|
colour | RedYellow |
---|
title | TODOSTARTED |
---|
|
Ongoing Patient Data Updates (including NHSBT)
...
Patients who have an open PKB Membership Membership
Status |
---|
colour | RedYellow |
---|
title | TODOSTARTED |
---|
|
- This is mostly done but the SQL will need amending to use the PKB membership rather than PV. -
https://jira.ukrdc.org/browse/PKB-110Whose records for a participating SendingFacility have been updated OR the NHSBT record for that patient has been updated (to update the Care Plan).
Status |
---|
colour | RedYellow |
---|
title | TODOSTARTED |
---|
|
Again this is mostly done but does not currently refer to NHSBT.
https://jira.ukrdc.org/browse/PKB-113 needs to be done to contain a list of which units have "gone live".
...