Page Comparison

...

All Patients for a Sending Facility

With an open PV Membership

Without a DeathTime

One record per UKRDCID.

Output

PKB ProgramMembership Record, sent to UKRDC

A28 Demographic Message (no ZTM Segment) sent to PKB

Method

pkbdump

Initial Data Send

Criteria

All Patients for a Sending Facility

With an open PKB Membership (or PV (and not dead) - at the point of the initial send this should be identical). 

One record per PID. 

SendingExtracts PVMIG/PV/UKRDC are acceptable. - we should sending the complete historic record as far as possible  (minimum is the PV feed) 

Output

This should be full PV Dump 

Only those Message Types requested by the Unit. (As in if a Unit has requested that we don't send certain data, for example medications, if they are sending already sending that data to PKB from their central system and do not want a feed from the Renal System duplicating). - https://jira.ukrdc.org/browse/PKB-99

Method

...

pkbdump 

Status
colour Green title DONE

New Patient Demographic Send

Criteria

Patients who attend have a PV record from Any Sending Facility which is Enabled. (GS: Should this be everyone to match the Initial Demograhic Send?)Who have received a PV XML File  enabled and no PKB membership. (

(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) 

One record per UKRDCID. 

Output

PKB ProgramMembership Record, sent to UKRDCUKRDC 

A28 Demographic Message (no ZTM Segment) sent to PKB 

Method

UKRDC Process va MirthMirth 

New Patient Data Send

Criteria

Patients who attend a Sending Facility which is Enabled.have a newly created PKB membership perhaps triggered as part of the PKB creation. 

Who have received a PV XML File  File for the first time  (GS: How does this work with UKRDC Feeds ?)

Output

currently can only work if the feed includes a PKB membership indicator/new membership flag in some way) 

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. 

Output

This should be full PV Dump 

Only those Message Types requested by the Unit, sent to PKB. -https://jira.ukrdc.org/browse/PKB-99

Method

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. 

New Death Demographic Notifications

...

Patients who have an open PKB Membership. 

Who have an updated TRACING record containing a DeathTime which occured occurred more than two weeks ago. 

One record per UKRDCID 

Output

PKB ProgramMembershop ProgramMembership Record - with an End Date, sent to UKRDC. 

A28 Demographic Message (no ZTM Segment) sent to PKB 

Method

UKRDC Process via MirthMirth 

Ongoing Patient Data Updates (including NHSBT)

...

Patients who have an open PKB MembershipPKB Membership 

Whose records for a participating SendingFacility have been updated OR the NHSBT record for that patient has been updated (to update the Care Plan). 

Only PV and UKRDC SendingExtracts should be counted.

Output

Only those Message Types containing updated data, which have been requested by the Unit. - https://jira.ukrdc.org/browse/PKB-99

Method

UKRDC Process via Mirth

Changes to PV Feed

We need to amend the pv_to_rda logic so that if the site is enabled ( https://jira.ukrdc.org/projects/PKB/issues/PKB-113 ) incoming PV XML files will be accepted from units that have gone live with PKB - hence will not have a PV ProgramMembership.