1 / 6

Full metadata Subscription and Pull-style Notification (FSPN)

DSUB.b or. Full metadata Subscription and Pull-style Notification (FSPN). Brief Profile Proposal for 2012/13 presented to the ITI Planning Committee Webinar Mauro Zanardini (consorzio Arsenàl.IT) October, 10 th October 2012. Effort Estimates. The work requested to ITI is:

hazina
Download Presentation

Full metadata Subscription and Pull-style Notification (FSPN)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DSUB.b or Full metadata Subscription and Pull-style Notification (FSPN) Brief Profile Proposal for 2012/13 presented to the ITI Planning Committee Webinar Mauro Zanardini (consorzio Arsenàl.IT) October, 10th October 2012

  2. Effort Estimates The work requested to ITI is: • To extend functionalities of DSUB (Document metadata Subscription) profile. (full metadata subscription, extend payload content, multiple patient subscription etc.) • To Evaluate how creating systems of notification adaptable for Workflow Management Systems based on XDW. • To define a new modality to convey notifications to Recipients that can’t show public IP or that can’t grant continuity of service. • To find modalities to create subscription, and to deliver notification only if allowed by access policies.

  3. The Problem Data coming from the Veneto region (4.900.000 habitants): Actors not allowed use a DSUB system of notification: • 3500 GPs; • 14.500 Hospital Clinicians; Clinical processes in which they are involved: • 60.000.000 prescriptions per year: for specialist consultation, laboratory investigation or pharmaceutical services. Each prescription involves at least 2 notifications to the Requester; • 500.000 patients can be potentially involved in telemonitoring processes; • 750.000 hospitalizations per year; Each GP receives almost 600 notifications/week related to ePrescriptions, and has to follow the telemonitoring processes for almost 140 patients, who collect data every day and generate alarms which have to be readily managed.

  4. Use Case (1/2): A distributed clinical process in which participants involved are not known at the beginning of the workflow, but they have to be enrolled readily: e.g. telemonitoring process Enrolling specialists or notiffy to a specialist of reference XD* Infrasctucture Notify publishing of data to the GP

  5. Use Case (2/2): Clinician that want to be acknowledged for specific workflow: e.g. ePrescription/eReferral process Notificaiton based on Workflow updates XD* Infrasctucture Request

  6. Role of existing profiles: DSUB: • Does not allow to subscribe and deliver other objects than documents • Requires the Recipient to share public IP, and to grant continuity of service. • Allows only push-and-forget style for notification Query Approach: • Large number of useless queries to the registry. • High complexity of requests made by the Recipient for multiple patientIdand multiple content (this two points can involve overloading for a registry) • There is not a system to track events occurred and notified, but not acknowledged by the Recipient. It can be done only with a notification queue manager and outpacing the push-and-forget style. • In a query scenario the Recipient has to know what it would like to find (or the patient related)

More Related