SYSTEMS AND METHODS FOR SEEKABLE LAYER FILE ENCODING AND DECODING

• US 20090157748A1
• Filed: 12/14/2007
• Published: 06/18/2009
• Est. Priority Date: 12/14/2007
• Status: Abandoned Application

• Current Assignee: McKesson Corp.
• Original Assignee: Mckesson Financial Holdings Limited (McKesson Corp.)
• Inventors: Hess, John M.
• Application Number:
  US11/957,171
• Publication Number:
  US 20090157748A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 15/00 ICT specially adapted for medical reports, e.g. generation or transmission thereof
• CPC Class Codes: G16H 20/10 relating to drugs or medications, e.g. for ensuring correct administration to patients
• CPC Class Codes: G16H 40/67 for remote operation

Abstract

The present invention provides for efficient random access to the contents of files encoded with two or more layers of standard or custom encoding. In accordance with an embodiment of the present invention, a file of transaction messages are encoded by dividing the file into multiple discretely-sized, blocks of data are independently encoded. When information in a certain transaction message within the unencoded file is requested, only the encoded block(s) containing that transaction message is decoded.

Claims

1. A method for retrieving encoded transaction information associated with a pharmacy transaction, comprising:

receiving a request for the transaction information;

searching an index of data elements associated with pharmacy transaction messages in a plurality of data files to identify at least a first data file including the requested transaction information and at least one location of the transaction information within the first data file;

opening a first data file, wherein the data file includes a header and a plurality of data blocks of encoded pharmacy transaction messages;

reading the header and determining a first data block in the first data file that contains the first byte of the requested transaction information;

decoding at least the first data block and outputting the transaction information; and

generating a report based at least in part on the transaction information, and presenting the report to a user.

2. The method of claim 1, wherein the step of decoding includes decoding a second data block if the transaction information is not wholly contained within the first data block.

3. The method of claim 1, wherein the step of decoding includes decrypting and decompressing the first data block.

4. The method of claim 1 wherein the transaction information comprises a data element in a pharmacy transaction message generated at least in part by a pharmacy.

5. The method of claim 1, wherein the first data file is a nested record structure file format.

6. The method of claim 1, wherein the step of reading the header includes reading the sizes of the data blocks in the first data file.

7. The method of claim 1, wherein the step of reading the header includes reading at least one of the sizes of the data blocks in the first data file, a type of encoding, or a data segment size utilized to encode the first data file into data blocks.

8. The method of claim 1, wherein the at least one location of the transaction information within the first data file comprises a position in the unencoded first data file, and wherein the step of determining a first data block in the first data file that contains the first byte of the requested transaction information includes determining the first data block based at least in part on the position in the unencoded first data file and a data segment size utilized to encode the first data file into data blocks.

9. A method for storing transaction information associated with a pharmacy transaction in a HIPAA compliant data file, comprising:

receiving a HIPAA compliant data file including a plurality of transaction messages;

indexing in an index repository the data file on predetermined data elements associated with transaction messages;

encoding the data file utilizing fixed-sized data segments of the data file to generate a plurality of encoded data blocks;

generating a header that includes size indicators for the encoded data blocks;

generating an encoded data file comprising the header and the encoded data blocks; and

storing in memory the encoded data file.

11. The method of claim 11, further including storing the index repository.

10. The method of claim 11, where in the step of encoding includes compressing and encrypting the data file.

12. The method of claim 11, further including verifying the contents of the encoded data file.

13. The method of claim 12, further comprising generating a first checksum value for the data encoded into the encoded first data file, and wherein verifying the contents of the encoded data file includes comparing the first checksum value to a second checksum value associated with a decoded version of the encoded data file.

14. The method of claim 11, wherein generating a header comprises generating a header that includes the size indicator for each encoded data block generated, a type of encoding, or a data segment size utilized to encode the first data file into data blocks.

15. A system for retrieving encoded transaction information associated with a pharmacy transaction, comprising:

a memory comprising a plurality of encoded data files, the encoded data filed including pharmacy transaction messages, and an index repository of indexed data elements associated with the pharmacy transaction messages in a plurality of data files; and

a processor in communication with the memory, wherein the processor is configured to;

receive a request for the transaction information;

search the index repository to identify at least a first data file including the requested transaction information and at least one location of the transaction information within the first data file;

open a first data file, wherein the first data file includes a header and a plurality of data blocks of encoded pharmacy transaction messages;

read the header and determine a first data block in the first data file that contains the first byte of the requested transaction information; and

decode at least the first data block and output the transaction information.

16. The system of claim 16, wherein the processor is further configured to generate a report based at least in part on the transaction information.

17. The system of claim 16, wherein the processor is further configured to decode a second data block if the transaction information is not wholly contained within the first data block.

18. The system of claim 16, wherein the processor decodes the first data block by decrypting and decompressing the first data block.

19. The system of claim 16, wherein the header read by the processor includes sizes of the data blocks in the first data file.

20. The system of claim 16, wherein the at least one location of the transaction information within the first data file comprises a position in the unencoded first data file, and the first data block in the encoded first data file that contains the first byte of the requested transaction information is determined based at least in part on the position in the unencoded first data file and a data segment size utilized to encode the first data file into a plurality of data blocks.