System and methods of pre-fetching content in one or more repositories

• US 9,826,054 B2
• Filed: 12/31/2013
• Issued: 11/21/2017
• Est. Priority Date: 06/21/2013
• Status: Active Grant

• Current Assignee: Hyland Switzerland, Sarl
• Original Assignee: Kofax International Switzerland Sàrl (Kofax Incorporated)
• Inventors: Gasser, Otto Hunter, Romatoski, Jeffrey Allen, Atanasiu, Razvan
• Primary Examiner(s): Wang, Liangche A
• Application Number:
  US14/145,145
• Publication Number:
  US 20140379837A1
• Time in Patent Office: 1,421 Days
• Field of Search: 709201, 709213, 709217, 709219, 709223, 709225, 709226
• CPC Class Codes: H04L 67/5681 Pre-fetching or pre-delivering data based on network characteristics

Abstract

A method of pre-fetching content that includes determining a possible future use of a content and determining if the content is available in a cache repository. If the possible future use is determined and the content is determined to be unavailable in the cache repository, the method retrieves the content from a remote repository and provides the retrieved content to a content consumer.

Claims

1. A method of pre-fetching content, comprising:

forwarding content from a cache repository to either or both of;

an active central repository of a primary system; and

a vendor neutral archive (VNA) of the primary system;

forwarding metadata associated with the content to either or both of;

a registry of the primary system; and

the VNA of the primary system;

wherein the content is forwarded to either or both of the active central repository of the primary system and the VNA of the primary system for replication to either or both of;

an active central repository of a secondary system secondary system; and

a VNA of the secondary system; and

wherein the metadata is forwarded to either or both of the registry of the primary system and the VNA of the primary system for replication to a registry of the secondary system;

tracking one or more broadcasted messages;

scanning the one or more broadcasted messages to determine if the one or more broadcasted messages include an identifier of the content;

if the one or more broadcasted messages are determined to include the identifier of the content, determining if the content is available in the cache repository;

if the content is determined to be unavailable in the cache repository, retrieving the content from a remote repository; and

storing the retrieved content in the cache repository for accessing by a content consumer prior to receiving a request for the content from the content consumer.

2. The method of claim 1, wherein the storing the retrieved content to the content consumer is performed prior to use of the content by the content consumer.

3. The method of claim 1, further comprising determining a possible future use of the content, wherein the determining the possible future use of the content includes monitoring Health Level-7 (HL 7) messages.

4. The method of claim 1, further comprising determining a possible future use of the content, wherein the determining the possible future use of the content is triggered by a Health Level-7 (HL 7) Order Message (ORM) information;

and

wherein the HL 7 ORM information comprises or corresponds to a scheduled procedure data.

5. The method of claim 1, wherein the identifier of the content comprises metadata corresponding to the content, the metadata indicating one or more of:

a size of a DICOM image represented in the content;

one or more dimensions of the DICOM image represented in the content;

a modality used to create the DICOM image represented in the content;

a bit depth of the DICOM image represented in the content;

one or more settings of medical imaging equipment used to capture the DICOM image represented in the content;

a patient medical history;

one or more patient demographics;

a patient immunization status;

a patient'"'"'s medical allergies;

a patients'"'"' vital signs;

billing information corresponding to a patient;

a means by which the content was created;

a purpose of the content;

a time and date of content creation;

a creator of the content;

an author of the content;

one or more standards used in generating the content; and

information regarding a history of the content.

6. The method of claim 1, wherein the retrieving the content from the remote repository is performed using Cross-Enterprise Document Reliable Interchange (XDR) between the remote repository and the cache repository.

7. The method of claim 1, wherein the content comprises DICOM image data.

8. The method of claim 1, further comprising, in response to determining the remote repository is unavailable, retrieving the content from a backup remote repository;

and

storing the retrieved content in the cache repository for accessing by the content consumer prior to the request from the content consumer.

9. The method of claim 1, wherein the remote repository comprises a vendor neutral archive (VNA) storing the content, metadata associated with the content, and a manifest document comprising diagnostic imaging references of content into a Cross-Enterprise Document Sharing for Imaging (XDS-I) framework.

10. The method of claim 1, wherein the one or more broadcasted messages are transmitted in HL7 format, and wherein each message independently comprises one of:

a patient record;

a billing information record;

a laboratory record;

a patient admission record; and

a patient check-up record.

11. The method of claim 1, wherein the remote repository comprises a vendor neutral archive (VNA) comprising a standard interface allowing access to the content in the remote repository regardless of an identity of a vendor producing a device used to generate the content.

12. The method of claim 1, wherein retrieving the content from the remote repository comprises:

retrieving a manifest document comprising unique identifiers of the content from an active central repository; and

retrieving the content from a vendor neutral archive (VNA) of the remote repository based on the unique identifiers in the manifest document.

13. A system for pre-fetching one or more documents, comprising:

a content consumer;

a cache repository connected to the content consumer;

a remote repository connected to the cache repository; and

an application communicatively connected to the cache repository for;

forwarding content from the cache repository to either or both of;

an active central repository of a primary system; and

a vendor neutral archive (VNA) of the primary system;

forwarding metadata associated with the content to either or both of;

a registry of the primary system; and

the VNA of the primary system;

wherein the content is forwarded to either or both of the active central repository of the primary system and the VNA of the primary system for replication to either or both of;

an active central repository of a secondary system secondary system; and

a VNA of the secondary system; and

wherein the metadata is forwarded to either or both of the registry of the primary system and the VNA of the primary system for replication to a registry of the secondary system;

tracking one or more messages transmitted at least one of to and from the content consumer, and scanning the one or more messages to determine if the one or more messages include an identifier of the content,

wherein if the one or more messages transmitted at least one of to and from the content consumer are determined to include the identifier of the content, determining if the content is available in the cache repository; and

upon negative determination, storing in the cache repository a copy of the content retrieved from the remote repository.

14. The system of claim 13, wherein the content consumer, the cache repository and the remote repository communicate to each other using Cross-Enterprise Document Sharing for Images (XDS-I).

15. The system of claim 13, wherein the one or more messages are Health Level-7 (HL 7) messages;

wherein the cache repository monitors the HL 7 messages to identify a possible future use of the document;

wherein the possible future use of the document is a scheduled procedure data that utilizes the document; and

wherein the content consumer retrieves the document from the cache repository instead of the remote repository at a time of the scheduled procedure data.

16. The system of claim 13, wherein the cache repository retrieves the copy of the document from the remote repository only if the cache repository does not contain the document at a time a possible future use of the document is identified.

17. A computing device having a non-transitory computer readable storage medium containing one or more instructions to:

forward content from a cache repository of to either or both of;

an active central repository of a primary system; and

a vendor neutral archive (VNA) of the primary system;

forward metadata associated with the content to either or both of;

a registry of the primary system; and

the VNA of the primary system;

wherein the content is forwarded to either or both of the active central repository of the primary system and the VNA of the primary system for replication to either or both of;

an active central repository of a secondary system secondary system; and

a VNA of the secondary system; and

wherein the metadata is forwarded to either or both of the registry of the primary system and the VNA of the primary system for replication to a registry of the secondary system; and

track one or more broadcasted Health Level-7 (HL7) messages;

scan each of the one or more broadcasted HL 7 messages if the one or more broadcasted HL 7 messages include an identifier of the content;

if the one or more HL 7 messages are determined to include the identifier of the content, determine if the content is available in the cache repository;

if the content is determined to be unavailable in the cache repository, retrieve the content from a remote repository; and

provide the retrieved content to a content consumer by storing the retrieved content in the cache repository.

18. The computing device of claim 17, wherein the instruction to provide the retrieved content to the content consumer is performed prior to use of the content by the content consumer.

19. The computing device of claim 17, further comprising an instruction to store the retrieved content from the remote repository to the cache repository.