Systems with message integration for data exchange, collection, monitoring and/or alerting

• US 8,306,831 B2
• Filed: 01/10/2005
• Issued: 11/06/2012
• Est. Priority Date: 01/10/2005
• Status: Active Grant

• Current Assignee: Snap, Inc.
• Original Assignee: International Business Machines Corporation
• Inventors: Eisenberger, George, McCulloch, Edgar H. III, Richards, Thomas L. II
• Primary Examiner(s): Rines, David
• Application Number:
  US11/032,590
• Publication Number:
  US 20060168043A1
• Time in Patent Office: 2,857 Days
• Field of Search: 705/2, 705/3, 705/1, 3/2, 3/3
• US Class Current: 705/3
• CPC Class Codes: G16H 70/40 relating to drugs, e.g. their side effects or intended usage
• CPC Class Codes: G16H 80/00 ICT specially adapted for facilitating communication between medical practitioners or patients, e.g. for collaborative diagnosis, therapy or health monitoring
• CPC Class Codes: Y02A 90/10 Information and communication technologies [ICT] supporting adaptation to climate change, e.g. for weather forecasting or climate simulation

Abstract

Methods, systems and related products for collaborative exchange of healthcare data using a computer network are configured to: (a) receive a participating Subscriber'"'"'s request for publication of selected clinical data from participating Publishers that have respective Publisher repositories of clinical data; (b) determine whether respective Publishers approve publication of their clinical data for the selected clinical data and the requesting Subscriber; and (c) electronically forward the selected clinical data from those participating Publishers that approve publication of the requested selected clinical data to the requesting Subscriber.

Claims

1. A method for facilitating collaborative exchange of healthcare data using a computer network of processor-based Subscriber and Publisher participants, comprising:

generating, in an electronic collaborative data sharing system, an electronic catalog of clinical data topics, wherein the clinical data topics are representative of participating Publishers'"'"' repositories of clinical data;

presenting the electronic catalog of clinical data topics to participating Subscribers;

receiving in the electronic collaborative data sharing system, a participating Subscriber'"'"'s request for publication of a clinical data topic, wherein the Subscriber'"'"'s request is selected from the electronic catalog of clinical data topics;

determining, by the system, which of the participating Publishers store clinical data relevant to the selected data topic, in their respective clinical data repositories;

forwarding the Subscriber request from the system to each of the Publishers determined by the system to store clinical data relevant to the selected clinical data topic;

determining in the system whether respective Publishers approve the Subscriber request to publish their clinical data relevant to the selected clinical data topic to the Subscriber;

establishing a Subscriber-specific authorized topic subscription for each Publisher approving the Subscriber request; and

electronically forwarding from the system to the requesting Subscriber clinical data responsive to the Subscriber request from those participating Publishers that approve the publication of their clinical data relevant to the selected clinical data topic to the requesting Subscriber.

2. A method according to claim 1, wherein the Publishers comprise respective Publisher Gateways, and wherein the electronically forwarding the clinical data to the requesting Subscriber responsive to the Subscriber request comprises electronically transmitting the requested clinical data from the Publisher Gateways to an intermediary Message Flow Server, the Message Flow Server then forwarding the transmitted clinical data to at least one approved Subscriber.

3. A method according to claim 1, wherein the topic comprises a plurality of data field parameters.

4. A method according to claim 3, further comprising:

receiving requests for publication of one or more healthcare topics listed in the electronic catalog from a plurality of Subscribers; and

for each Publisher approving a said request for publication from a said Subscriber, establishing a separate Subscriber-specific authorized topic for that said Subscriber;

wherein the electronically forwarding the clinical data to the Subscriber responsive to the Subscriber request comprises automatically routing publications of clinical data from Publishers to Subscribers with authorized topic subscriptions using an intermediary Message Flow Server that controls the routing according to the authorized topic subscriptions.

5. A method according to claim 1, wherein the electronically forwarding the clinical data to the Subscriber responsive to the Subscriber request comprises forwarding the clinical data in a message format with a topic header.

6. A method according to claim 1, wherein the electronically forwarding the clinical data to the Subscriber responsive to the Subscriber request is selectively carried out to a respective Subscriber using a Subscriber-selected communication destination and format.

7. A method according to claim 6, wherein the selected communication format comprises at least one of email, HL-7 messaging, and electronic communication with a Subscriber repository database.

8. A method according to claim 6, wherein the communication destination comprises at least one of a wireless communication device, a personal computer, and a mainframe computer.

9. A method according to claim 1, further comprising allowing each Publisher to approve or deny a Subscriber'"'"'s request for selected clinical data, and if approved, establishing Publisher and topic-specific authorized Subscriber subscriptions for the requested selected clinical data, then electronically forwarding Publisher healthcare data from a respective Publisher to those Subscribers having authorized subscriptions therefor generally concurrently.

10. A method according to claim 1, further comprising hosting a web application at a hub site that is configured to administer participant access and confirm that a Subscriber is authorized to request the selected clinical data topic before forwarding a respective Subscriber request to one or more Publishers.

11. A method according to claim 1, further comprising,

notifying the Publishers of the Subscriber'"'"'s publication request as a publication topic data request of the selected clinical data, the topic data request being displayed on a web portal at each Publisher;

then allowing each Publisher to electronically review and approve or deny the publication request from the requesting Subscriber.

12. A method according to claim 1, further comprising transmitting Publisher clinical data as messages to a Message Flow Server, wherein the electronically forwarding requested selected clinical data is carried out only for those Publishers that approve the publication request for the requesting Subscriber, and only for those Publisher messages which contain data corresponding to the selected clinical data request.

13. A method according to claim 1, further comprising:

having each Publisher automatically electronically monitor their respective repositories of clinical data for adverse drug events; and

generating an electronic adverse drug event alert that is automatically transmitted to at least one selected Subscriber in response to an adverse drug event identified during the monitoring of the repositories.

14. A method according to claim 1, further comprising electronically monitoring Publisher repositories and automatically electronically generating a public health, safety, disease or exposure alert to at least one Subscriber.

15. A method according to claim 1, further comprising;

providing the electronic catalog of topics to the requesting Subscriber through an Administrative Server, each topic having defined data content of interest; and

allowing the requesting Subscriber to select an existing topic in the catalog to initiate a request for selected clinical data.

16. A method according to claim 15, further comprising allowing a Subscriber to create a new topic of interest associated with a selected clinical data request that is then stored in the topic catalog.

17. A method according to claim 2, wherein the Publishers comprise healthcare providers, and wherein the respective Publisher Gateways are configured to electronically omit personal patient identifiers before transmitting clinical data in response to the requested clinical data in a message format to the Message Flow Server.

18. A method according to claim 17, further comprising assigning a unique identifier to the Publisher message that is traceable to the originating source Publisher and indirectly traceable to a patient.

19. A method according to claim 1, wherein requests for publication of selected clinical data topics from Subscribers are selectively forwarded to Publishers by electronically filtering the requests based on an electronic registry of authorized participants and/or an authorized level of participation of the participants.

20. A method according to claim 1, wherein the Publisher provides the requested selected clinical data as a publication message comprising an open-standard messaging format.

21. A method according to claim 4, further comprising allowing a respective Publisher to cancel a subscription authorization to a particular Subscriber and/or for a particular selected clinical data topic.

22. A method according to claim 1, wherein each Subscriber publication request is associated with a defined topic trigger event of diagnosis, symptoms, demographic criteria, medication order, lab observation, lab results, therapeutic procedure and/or procedure results.

23. A method according to claim 2, further comprising electronically storing patient data records in a repository associated with a respective Publisher Gateway disposed inside a security zone of said respective Publisher for a temporally limited interval.

24. A method of providing a web-based collaborative data sharing system to facilitate the transfer of clinical data from participating processor-based Publishers to participating processor-based Subscribers over a computer network, comprising:

generating, in an electronic collaborative data sharing system, an electronic catalog of clinical data topics, wherein the clinical data topics are representative of participating Publishers'"'"' repositories of clinical data;

presenting the electronic catalog of clinical data topics to participating Subscribers;

hosting a web application at a hub site that is configured to administer participant access and allow only participating Subscribers to access the system;

electronically forwarding at least one topic data request from a plurality of Subscribers to each Publisher determined to store clinical data relevant to the selected topic data request;

electronically determining, for each of the Publishers determined to store clinical data relevant to the selected topic data request and each Subscriber in the plurality of Subscribers, whether the Publisher approves the request to publish clinical data relevant to the selected clinical data topic to the Subscriber;

electronically establishing a Subscriber-specific authorized topic subscription for each Publisher approving the Subscriber request;

electronically receiving Publisher messages with data associated with the topic data request at a Message Flow Server; and

electronically selectively forwarding Publisher messages from the Message Flow Server to those Subscribers approved by respective Publishers for the at least one topic data request.

25. A method according to claim 24, further comprising allowing each Publisher to review and electronically approve or deny the topic data requests from the requesting Subscribers.

26. A method according to claim 25, wherein electronically selectively forwarding Publisher messages from the Message Flow Server to only Publisher-approved Subscribers is carried out only for those Publisher messages which contain data matching the approved topic data request from a respective Publisher.

27. A method according to claim 24, further comprising:

allowing each respective Publisher to electronically review its own data records to determine if any electronic data records match the Subscriber topic data request; and

sending a Publisher message with data that matches the Subscriber topic data request to the Message Flow Server such that the Publisher message is accessible to each approved Subscriber.