US20220197954A1 - System and methods for metadata management in content addressable storage - Google Patents
System and methods for metadata management in content addressable storage Download PDFInfo
- Publication number
- US20220197954A1 US20220197954A1 US17/565,280 US202117565280A US2022197954A1 US 20220197954 A1 US20220197954 A1 US 20220197954A1 US 202117565280 A US202117565280 A US 202117565280A US 2022197954 A1 US2022197954 A1 US 2022197954A1
- Authority
- US
- United States
- Prior art keywords
- content addressable
- addressable storage
- query
- metadata
- content
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/903—Querying
- G06F16/90335—Query processing
- G06F16/90339—Query processing by using parallel associative memories or content-addressable memories
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F15/00—Digital computers in general; Data processing equipment in general
- G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/13—File access structures, e.g. distributed indices
- G06F16/137—Hash-based
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/14—Details of searching files based on file metadata
- G06F16/148—File search processing
- G06F16/152—File search processing using file content signatures, e.g. hash values
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/14—Details of searching files based on file metadata
- G06F16/156—Query results presentation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/182—Distributed file systems
- G06F16/1824—Distributed file systems implemented using Network-attached Storage [NAS] architecture
- G06F16/1827—Management specifically adapted to NAS
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/185—Hierarchical storage management [HSM] systems, e.g. file migration or policies thereof
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
- G06F16/2471—Distributed queries
Definitions
- This disclosure relates to Content Addressable Storage for handling, storing, and distributing medical imaging information and, more specifically, to metadata management for CAS systems.
- Many files stored in computer systems represent data that is not expected to change over time.
- the percentage of files that are expected to not change can range up to 90% of the total files in the system.
- Examples of data and files that are expected not to change include medical images, images of cancelled bank checks, images collected by oil and gas exploration, surveillance videos, television news clips, and many types of archive and historical data. This is in strong contrast to files that are expected to change regularly, such as a database file, a word processing document that is being edited, and any type of file that represents current state, such as a file holding cumulative email messages as they arrive.
- CAS Content Addressable Storage
- a “handle” (not necessarily a file location) or a GUID (globally unique identifier) is created for each stored object. This handle can be created based on known techniques.
- CAS stores information that can be retrieved based on its content, not its storage location.
- a CAS system comprises storage nodes, where data is physically kept, and access nodes, where information on the data's location on the storage nodes are kept.
- new documents are passed to a CAS device, they are hashed, then stored based on that hash rather than with a directory table.
- Data is stored and retrieved with the resulting hash rather than based on a physical storage location or by using a hierarchical file system.
- Metadata even if it were embedded in or part of the content to be stored in the CAS, would not be searchable. If the application server did not itself store a particular image or other content to a CAS, then it would not know the GUID or handle of the content and would not be able to retrieve it.
- Embodiments of the systems, methods, and devices described herein overcome problems of the prior art by allowing a user to search for content that has been stored in content addressable storage, or CAS, even if that content was not stored by the local application server.
- Systems with multiple application servers, and perhaps even application servers that are of a heterogeneous nature receive content to be stored and, if certain criteria are met, store the content in a CAS repository. In some cases, the content may be stored in more than one CAS repository and will therefore be replicated in order to provide some redundancy of the data.
- the CAS server When storing the data to a CAS repository, the CAS server also collects and stores metadata associated with the content. The metadata can also be replicated over multiple CAS systems.
- the search can be performed directly on the application server, which may then search the metadata for content that it has stored.
- the application server may also send queries to CAS servers, which can then perform the search on the metadata associated with the CAS content stored there.
- the CAS content can then all be sent back to the application server, compiled (perhaps deleting or flagging duplicates of CAS content returned), and returned as a results set to the user.
- a user can search the distributed CAS servers directly and can receive compiled results directly from the CAS servers.
- a computer-implemented method for managing metadata in a content addressable storage system includes receiving a file for storage at a content addressable storage server, the file comprises a header and data, and wherein the content addressable storage server stores and retrieves the data based on content of the data rather than with a hierarchical file system; automatically obtaining with one or more computer processors metadata associated with the data from the header of the file; storing the metadata in a metadata storage device, wherein the metadata is stored in association with the data stored in the content addressable storage server; receiving a query from a requester for content at the content addressable storage server; searching the metadata storage device for content related to the received query; and when the metadata associated with the file is indicated by the query retrieving the file stored in the content addressable storage; and sending the retrieved file to the requester.
- a computer-implemented method for managing metadata in a content addressable storage system includes: receiving one or more files for storage at a content addressable storage server, wherein each of the one or more files comprises a header and data, and wherein the content addressable storage server stores and retrieves the data based on content of the data rather than with a hierarchical file system; automatically obtaining with one or more computer processors metadata associated with the data from the header of each of the one or more files; storing the metadata in a metadata storage device, wherein the metadata is stored in association with the data stored in the content addressable storage server; receiving a first query from a requester for content at an application server; searching locally at the application server for one or more files related to the first query; sending a second query, related to the first query, to the content addressable storage server; receiving one or more files related to the second query from the content addressable storage server; and sending to the requester the one or more files found locally based on the first query and the one or more files received from the content addressable storage server;
- a computer-implemented system for managing metadata in a content addressable storage system includes a content addressable storage system configured to: receive a file for storage, said file to be stored using content addressable storage; store metadata associated with the file in a storage mechanism for storing metadata for content addressable storage; receive a query from a requester for content; search the metadata storage mechanism for content related to the received query; and when the metadata associated with the file is indicated by the query: retrieve the file stored in the content addressable storage; and send the retrieved file to the requester.
- a computer-implemented system for managing metadata in a content addressable storage system comprising: a content addressable storage system configured to receive a file for storage, said file to be stored using content addressable storage; and store metadata associated with the file in a storage mechanism for storing metadata for content addressable storage; and an application server configured to: receive a first query from a requester for content; search locally for content related to the first query; send a second query, related to the first query, to the content addressable storage system; receive one or more files related to the second query from the content addressable storage system; and send to the requester the one or more files found locally based on the first query and the one or more files received from the content addressable storage system based on the second query.
- FIG. 1 illustrates a block diagram of a system for metadata management in a content addressable storage system.
- FIG. 2 is a block diagram representing an exemplary process for storing metadata in one or more CAS servers.
- FIG. 3 is a block diagram of an exemplary process for replicating objects and metadata.
- FIG. 4 depicts a block diagram of an exemplary process for retrieving CAS content from a CAS server.
- FIG. 5 depicts a block diagram of an exemplary process for retrieving CAS data via an application server.
- FIG. 1 illustrates a block diagram of a system for metadata management in a content addressable storage system.
- the network 101 may be the internet, an intranet, a dedicated wired network, one or more cables, a wireless network, or any other appropriate type of communication.
- the system may include one or more CAS servers 110 A-C. Each of these CAS servers may include or have thereto attached one or more storage systems 120 A-C.
- the storage systems 120 A-C may include one or more RAID storage systems, cloud storage, tape storage, optical disks, magnetic disks, and/or any other appropriate type of storage. There may be any number of CAS servers and each may have any number of storage systems 120 A-C.
- Two or more storage systems 120 A-C may reside on the same physical disk or storage, or each storage system 120 A-C may reside on one or more disks or other storage separate from all of the other storage systems 120 A-C.
- content stored in a CAS server 101 A-C may be retrieved based on a GUID, as is known in the art, or based on a search, as discussed herein.
- a CAS server 110 A-C when a CAS server 110 A-C receives content to store, it may store the content and metadata to the storage system 120 A-C.
- the content may be stored in the format in which it is received, or in flat files, directories, databases, or the like.
- the metadata may be stored in any fashion, including in a database, flat file, directory of files, or the like.
- the metadata may be stored in XML or other structured file as plain text and this plain text may be searchable.
- the metadata is stored in a database, and this database may be searchable.
- the CAS servers 110 A-C may be coupled via the network to one or more application servers 130 .
- the application server 130 may include or have thereto attached a storage system 150 .
- the storage system 130 like the storage system 120 A-C, may include one or more one or more RAID storage systems, cloud storage, tape storage, optical disks, magnetic disks, and/or any other appropriate type of storage.
- the application server 130 is used to receive one or more files, make a decision to store the file in CAS and to send the file and or metadata to a CAS server 110 A-C in order to store the CAS content and/or the metadata.
- the application server 130 may be used by a user using a client computer, e.g., client system 140 A, in order to query for content.
- client computer e.g., client system 140 A
- the user may submit a query for content to the application server 130 and the application server may attempt to respond to that query both by looking locally, including on its storage system 135 and by sending the query to one or more CAS servers 110 A- 110 C.
- one or more client systems 140 B- 140 C are coupled to the network 101 and may allow a user to query the CAS servers 110 A- 110 C via a client application directly without going through an application server 130 .
- FIG. 2 is a block diagram representing an exemplary process for storing metadata in one or more CAS servers.
- content is received.
- receiving content may include receiving DICOM images, images, historical data, video or other content.
- the content may be received, e.g., at an application server 130 .
- CAS Content Addressed Storage
- the unit of data may be provided as an input to a hashing function which generates a hash value that is used as the content address for the unit of data.
- a host computer sends a request to a content addressable storage system to retrieve a unit of data
- the host provides the content address (e.g., hash value) of the unit of data.
- the storage system determines, based on the content address, the physical location of the unit of data in the storage system, retrieves the unit of data from that location, and returns the unit of data to the host computer.
- the application server 130 may store the content locally in a storage system 135 .
- the application server may also store metadata associated with the content locally on the application server 130 or in the storage system 135 .
- the content and the metadata may be correlated.
- the metadata may be stored in a database or an XML file and may include a pointer or reference to the content (such as a file location or unique database ID depending on the implementation and the type of data). The locally-stored metadata may later be searched and the content and metadata served to a searcher.
- Methods for choosing what data to store in CAS storage and what content to not store in CAS may include data types (e.g., PDF files, images, and medical records may be indicated as CAS candidates) last modification date, identity of the providing system, indications in the metadata, compliance with Sarbanes-Oxley, age of the file, status of a project related to the file, size of the file, or ways known to those skilled in the art.
- data types e.g., PDF files, images, and medical records may be indicated as CAS candidates
- step 220 a determination is made to store the content at a CAS server 110 A-C, then the content is sent to a CAS server in step 230 , a metadata file is created in step 240 , and the content and metadata are associated with each other in step 250 .
- the application server may send the content to the CAS server in step 230 and the CAS server may create the metadata file in step 240 .
- the metadata file is created at the application server and both are sent to the CAS server.
- the metadata file may be associated with the content file (step 250 ) either at the application server or at the CAS server.
- the application server may send the content and/or the metadata to more than one server.
- the metadata corresponding to the CAS content may include any relevant data such as author, data owner, patient name (in the case of medical data), patient number, television episode title, creation date, etc.
- the metadata may be stored in a number of ways.
- the data may be stored in an XML file, in an unformatted text file, in a formatted text file, in a database entry, or in any other of a myriad of appropriate manners.
- the metadata may come from a DICOM header, text in the file, analysis of the file (e.g., size and modification date of the file), summary or metadata fields in the document, descriptive or other files associated with received file, or other sources of metadata. This stored metadata may then later be searchable.
- Associating the metadata with the content in step 250 may comprise including the GUID for the content in the metadata file or having a separate file, database entry, etc. that includes references to the metadata and the content.
- the CAS content and metadata may be distributed to multiple CAS servers.
- the CAS content and metadata may be distributed to multiple servers simultaneously or sequentially, in a hierarchical fashion where each CAS server distributes the data to one or more other CAS servers, or in any other appropriate manner or topology.
- the CAS content and metadata may not be distributed among CAS servers and step 260 may not be performed.
- distributing the CAS content and the metadata can provide for redundancy benefits and/or communication benefits (given that, as the result of distribution, the CAS content may be replicated at a location that is close on the network).
- a CAS server may be configured to replicate CAS objects. It may be useful to distribute the CAS content across multiple CAS servers for redundancy or other reasons. Depending on embodiment and other factors, a CAS server may replicate objects once it receives them, after a particular request for replications, during some preconfigured interval, or for any other appropriate reason.
- FIG. 3 is a block diagram of an exemplary process for replicating objects and metadata.
- a CAS server that has content to be replicated sends that content and the associated metadata to another CAS server. This can be accomplished, for example, using network 101 .
- the metadata may be embedded within, appended to, or separate from the content.
- step 320 the content and metadata are received by the receiving CAS server and, in step 330 , are parsed. After the data has been parsed, it is stored into a database in step 340 . How the metadata is parsed will depend on the embodiment and how the data is formatted. For example, if the metadata is in an XML file, then the XML file may be parsed based on the known format of the file and stored, in step 340 , into the metadata database.
- the metadata database may include separate fields for each of known element of metadata. For example, for a DICOM image, there are numerous known fields in the header, including patient name.
- the database that houses the metadata may have fields for these known elements of metadata.
- the database may have one or more free text or other fields that will allow for storage of unknown or uncategorized metadata, such as a “notes” section of a patient chart or a “description” section of a television episode. In some embodiments, all of the database fields may later be searchable jointly or separately.
- the database that stores the metadata may be replicated, distributed, or otherwise available to multiple CAS servers and multiple application servers (such as those depicted in FIG. 1 ).
- Each CAS server may have its own database and the metadata for the content stored at that CAS server is stored therein.
- a CAS server's database may also have metadata and information on finding associated CAS content for things that are stored at other CAS servers, even if that content is not also stored at that CAS server.
- the metadata may also be stored, in some embodiments, in storage other than a database.
- the metadata may be stored in a flat file, multiple flat files, or any other storage mechanism or searchable storage mechanism.
- FIG. 4 depicts a block diagram of an exemplary process for retrieving CAS content from a CAS server.
- a query is received, perhaps from a user using a client system 140 B.
- the query can be in SQL, a Boolean search string, a natural language search, or any other appropriate format.
- the search is sent to other CAS servers.
- a CAS server 110 B may send the query to other CAS servers 110 A and 110 C.
- the search might be performed only on the local metadata, looking only for locally-stored content.
- the search is performed locally in step 430 .
- the local search can then be compiled and sent to the requester immediately, or, as depicted, combined with any results received from remote CAS servers and then sent to the requester in step 450 .
- the local search is performed before or simultaneously with the forwarding of the query to other CAS servers. For example, in some embodiments, a local query is first made for a file and if the query is completely satisfied, then no query is distributed to the other CAS servers.
- the local query performed in step 430 can take any appropriate form and will depend on the embodiment and the format of the received query. For example, if the received query is an SQL query and the metadata is stored in a database, then the received SQL query or some modification thereof may be used to query the local data. If the received query is a Boolean search and the metadata is stored in a flat file, then a text search based on the Boolean query may be performed. Once matching metadata is found, then the associated CAS content is retrieved and made ready to send to the requester.
- the CAS server may await results from the other CAS servers. All of the received results are combined and forwarded in step 460 . For example, if a CAS server storing DICOM images requested more results for a particular patient name and patient ID, then the DICOM CAS server may send the request to multiple CAS servers in order to get any results for that patent stored on any of the other servers. The results may be checked for validity via a checksum or other assurance mechanism built into the system, or any other appropriate CAS procedures. Corrupted or otherwise invalid files may be excluded from or flagged in the CAS or in the result set sent to the requester.
- any duplicate files may be excluded from or flagged in the result set sent to the requester. Additionally, in some embodiments, if the remote CAS server does not send a response within a particular timeout period, the CAS server may no longer await results and may send out any received results in step 450 .
- the results sent to the requester in step 460 can take any appropriate form, including a single compressed file, a pointed to one or more accessible pieces of data that comprise the complete data set, or any other appropriate mechanism.
- FIG. 5 depicts a block diagram of an exemplary process for retrieving CAS data via an application server.
- the process depicted in FIG. 5 is similar to that depicted in FIG. 4 , except that the search is initiated first by a user to an application server.
- the application server then sends the request to multiple CAS servers.
- a user using a client system 140 A sends a request for data to an application server 130
- the application server 130 receives the request (step 510 )
- the application server 130 forwards the request to the CAS servers 110 A-C (step 520 )
- the application server searches locally (step 530 ), and receives or times out waiting for results from the CAS servers (steps 540 and 550 ).
- the results are sent to the client system 140 A (step 560 ).
- the local search in step 530 at the application server may be for CAS data, or it may be for other application data.
- the CAS servers 110 A-C store DICOM images and the application server 130 stores patient demographic and billing information
- the local results may be related to the demographics and billing history of the results and the results from the CAS servers 110 A-C may be DICOM images.
- results from the CAS servers may be checked not only for integrity (via checksums, e.g.), but also for duplicates.
- the duplicate results may be flagged or omitted from the search results sent.
- the computer systems such as the client system 140 A-C, the application server 130 , and the content addressable storage systems 110 A-C may include a bus or other communication mechanism for communicating information, and a processor coupled with the bus for processing information.
- the computer systems may have a main memory, such as a random access memory or other dynamic storage device, coupled to the bus.
- the main memory may be used to store instructions and temporary variables.
- the computer systems may also include a read-only memory or other static storage device coupled to the bus for storing static information and instructions.
- the computer systems may also be coupled to a display, such as a CRT or LCD monitor. Input devices may also be coupled to the computer system.
- Each computer system may be implemented using one or more physical computers or computer systems or portions thereof.
- the instructions executed by the computer system may also be read in from a computer-readable medium.
- the computer-readable medium may be a CD, DVD, optical or magnetic disk, laserdisc, carrier wave, or any other medium that is readable by the computer system.
- hardwired circuitry may be used in place of or in combination with software instructions executed by the processor.
- All of the methods and processes described above may be embodied in, and fully automated via, software code modules executed by one or more general purpose computers or processors, such as those computer systems described above.
- the code modules may be stored in any type of computer-readable medium or other computer storage device. Some or all of the methods may alternatively be embodied in specialized computer hardware.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- General Engineering & Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Library & Information Science (AREA)
- Computational Linguistics (AREA)
- Computer Hardware Design (AREA)
- Software Systems (AREA)
- Fuzzy Systems (AREA)
- Mathematical Physics (AREA)
- Probability & Statistics with Applications (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Provided is a content addressable storage (CAS) system that allows a user to request, either through an application server or directly to one or more CAS servers, files and content related to a query. In some embodiments, the content can be discovered by searching previously-stored metadata related to each file at the content addressable storage server. The search can also be replicated across multiple content addressable storage servers in order to obtain varied results and redundant results. Duplicate results may be flagged or omitted, ˜d the results are returned to the requester.
Description
- This application is a continuation of U.S. patent application Ser. No. 16/663,273, which is a continuation of U.S. patent application Ser. No. 15/331,775, now abandoned, filed Oct. 21, 2016, which is a continuation of U.S. patent application Ser. No. 14/335,813, filed Jul. 18, 2014, now abandoned, which is a continuation of U.S. patent application Ser. No. 12/605,036, filed Oct. 23, 2009, now U.S. Pat. No. 8,788,519, which claims priority pursuant to 35 U.S.C. § 119(e) to U.S. Provisional Patent Application No. 61/108,341, filed Oct. 24, 2008. The disclosures of which are hereby incorporated by reference in their entireties.
- This disclosure relates to Content Addressable Storage for handling, storing, and distributing medical imaging information and, more specifically, to metadata management for CAS systems.
- Many files stored in computer systems represent data that is not expected to change over time. In some systems, the percentage of files that are expected to not change can range up to 90% of the total files in the system. Examples of data and files that are expected not to change include medical images, images of cancelled bank checks, images collected by oil and gas exploration, surveillance videos, television news clips, and many types of archive and historical data. This is in strong contrast to files that are expected to change regularly, such as a database file, a word processing document that is being edited, and any type of file that represents current state, such as a file holding cumulative email messages as they arrive.
- Content Addressable Storage (CAS) technology can be used to store, different types of data including, by way of example, data that does not change over time. Generally, a “handle” (not necessarily a file location) or a GUID (globally unique identifier) is created for each stored object. This handle can be created based on known techniques. In one embodiment, CAS stores information that can be retrieved based on its content, not its storage location.
- For example, in some embodiments a CAS system comprises storage nodes, where data is physically kept, and access nodes, where information on the data's location on the storage nodes are kept. As new documents are passed to a CAS device, they are hashed, then stored based on that hash rather than with a directory table. Data is stored and retrieved with the resulting hash rather than based on a physical storage location or by using a hierarchical file system.
- As content, such as an image, is received, it can be received by an application server and stored locally at the application server, or if the data meets whatever criteria are set up for CAS storage, stored in the CAS storage. Any metadata or other searchable data is stored on the application server or its local storage. The problem with current systems that utilize CAS, however, is that an end user searches for data on an application server and that application server must know about the content stored in the CAS (e.g., the specific GUID) in order to retrieve it. Metadata, even if it were embedded in or part of the content to be stored in the CAS, would not be searchable. If the application server did not itself store a particular image or other content to a CAS, then it would not know the GUID or handle of the content and would not be able to retrieve it.
- These and other problems are addressed by the embodiments described herein.
- Embodiments of the systems, methods, and devices described herein overcome problems of the prior art by allowing a user to search for content that has been stored in content addressable storage, or CAS, even if that content was not stored by the local application server. Systems with multiple application servers, and perhaps even application servers that are of a heterogeneous nature, receive content to be stored and, if certain criteria are met, store the content in a CAS repository. In some cases, the content may be stored in more than one CAS repository and will therefore be replicated in order to provide some redundancy of the data. When storing the data to a CAS repository, the CAS server also collects and stores metadata associated with the content. The metadata can also be replicated over multiple CAS systems.
- When a user later attempts to search for data, the search can be performed directly on the application server, which may then search the metadata for content that it has stored. In some embodiments, the application server may also send queries to CAS servers, which can then perform the search on the metadata associated with the CAS content stored there. The CAS content can then all be sent back to the application server, compiled (perhaps deleting or flagging duplicates of CAS content returned), and returned as a results set to the user. In other embodiments, a user can search the distributed CAS servers directly and can receive compiled results directly from the CAS servers.
- In one embodiment a computer-implemented method for managing metadata in a content addressable storage system includes receiving a file for storage at a content addressable storage server, the file comprises a header and data, and wherein the content addressable storage server stores and retrieves the data based on content of the data rather than with a hierarchical file system; automatically obtaining with one or more computer processors metadata associated with the data from the header of the file; storing the metadata in a metadata storage device, wherein the metadata is stored in association with the data stored in the content addressable storage server; receiving a query from a requester for content at the content addressable storage server; searching the metadata storage device for content related to the received query; and when the metadata associated with the file is indicated by the query retrieving the file stored in the content addressable storage; and sending the retrieved file to the requester.
- In another embodiment, a computer-implemented method for managing metadata in a content addressable storage system, includes: receiving one or more files for storage at a content addressable storage server, wherein each of the one or more files comprises a header and data, and wherein the content addressable storage server stores and retrieves the data based on content of the data rather than with a hierarchical file system; automatically obtaining with one or more computer processors metadata associated with the data from the header of each of the one or more files; storing the metadata in a metadata storage device, wherein the metadata is stored in association with the data stored in the content addressable storage server; receiving a first query from a requester for content at an application server; searching locally at the application server for one or more files related to the first query; sending a second query, related to the first query, to the content addressable storage server; receiving one or more files related to the second query from the content addressable storage server; and sending to the requester the one or more files found locally based on the first query and the one or more files received from the content addressable storage server based on the second query.
- In yet another embodiment, a computer-implemented system for managing metadata in a content addressable storage system, includes a content addressable storage system configured to: receive a file for storage, said file to be stored using content addressable storage; store metadata associated with the file in a storage mechanism for storing metadata for content addressable storage; receive a query from a requester for content; search the metadata storage mechanism for content related to the received query; and when the metadata associated with the file is indicated by the query: retrieve the file stored in the content addressable storage; and send the retrieved file to the requester.
- In yet another embodiment, a computer-implemented system for managing metadata in a content addressable storage system, comprising: a content addressable storage system configured to receive a file for storage, said file to be stored using content addressable storage; and store metadata associated with the file in a storage mechanism for storing metadata for content addressable storage; and an application server configured to: receive a first query from a requester for content; search locally for content related to the first query; send a second query, related to the first query, to the content addressable storage system; receive one or more files related to the second query from the content addressable storage system; and send to the requester the one or more files found locally based on the first query and the one or more files received from the content addressable storage system based on the second query.
- These and other features and advantages of the invention will become apparent from the following description of embodiments. Neither this summary nor the following detailed description purports to define the invention. The invention is defined only by the claims.
- These and other features will now be described with reference to the drawings summarized below. These drawings and the associated description are provided to illustrate specific embodiments, and not to limit the scope of the invention.
-
FIG. 1 illustrates a block diagram of a system for metadata management in a content addressable storage system. -
FIG. 2 is a block diagram representing an exemplary process for storing metadata in one or more CAS servers. -
FIG. 3 is a block diagram of an exemplary process for replicating objects and metadata. -
FIG. 4 depicts a block diagram of an exemplary process for retrieving CAS content from a CAS server. -
FIG. 5 depicts a block diagram of an exemplary process for retrieving CAS data via an application server. - In the following detailed description, references are made to the accompanying drawings that illustrate specific embodiments in which the invention may be practiced. Electrical, mechanical, programmatic and structural changes may be made to the embodiments without departing from the spirit and scope of the disclosure. The following detailed description is, therefore, not to be taken in a limiting sense and the scope of the disclosure is defined by the appended claims and their equivalents.
-
FIG. 1 illustrates a block diagram of a system for metadata management in a content addressable storage system. InFIG. 1 , numerous computers and systems are all interconnected via anetwork 101. Thenetwork 101 may be the internet, an intranet, a dedicated wired network, one or more cables, a wireless network, or any other appropriate type of communication. The system may include one ormore CAS servers 110A-C. Each of these CAS servers may include or have thereto attached one ormore storage systems 120A-C. Thestorage systems 120A-C may include one or more RAID storage systems, cloud storage, tape storage, optical disks, magnetic disks, and/or any other appropriate type of storage. There may be any number of CAS servers and each may have any number ofstorage systems 120A-C. Two ormore storage systems 120A-C may reside on the same physical disk or storage, or eachstorage system 120A-C may reside on one or more disks or other storage separate from all of theother storage systems 120A-C. In some embodiments, content stored in a CAS server 101A-C may be retrieved based on a GUID, as is known in the art, or based on a search, as discussed herein. - As noted herein, when a
CAS server 110A-C receives content to store, it may store the content and metadata to thestorage system 120A-C. The content may be stored in the format in which it is received, or in flat files, directories, databases, or the like. The metadata may be stored in any fashion, including in a database, flat file, directory of files, or the like. In some embodiments, the metadata may be stored in XML or other structured file as plain text and this plain text may be searchable. In some embodiments, the metadata is stored in a database, and this database may be searchable. - The
CAS servers 110A-C may be coupled via the network to one ormore application servers 130. Theapplication server 130 may include or have thereto attached a storage system 150. Thestorage system 130, like thestorage system 120A-C, may include one or more one or more RAID storage systems, cloud storage, tape storage, optical disks, magnetic disks, and/or any other appropriate type of storage. In some embodiments, theapplication server 130 is used to receive one or more files, make a decision to store the file in CAS and to send the file and or metadata to aCAS server 110A-C in order to store the CAS content and/or the metadata. In some embodiments, theapplication server 130 may be used by a user using a client computer, e.g.,client system 140A, in order to query for content. The user may submit a query for content to theapplication server 130 and the application server may attempt to respond to that query both by looking locally, including on itsstorage system 135 and by sending the query to one ormore CAS servers 110A-110C. - In some embodiments, one or
more client systems 140B-140C are coupled to thenetwork 101 and may allow a user to query theCAS servers 110A-110C via a client application directly without going through anapplication server 130. -
FIG. 2 is a block diagram representing an exemplary process for storing metadata in one or more CAS servers. Instep 210, content is received. In some embodiments, receiving content may include receiving DICOM images, images, historical data, video or other content. The content may be received, e.g., at anapplication server 130. - Content Addressed Storage (CAS) is a technique by which a unit of data stored on a storage system is accessed using an address that is derived from the content of the unit of data. As an example, the unit of data may be provided as an input to a hashing function which generates a hash value that is used as the content address for the unit of data. When a host computer sends a request to a content addressable storage system to retrieve a unit of data, the host provides the content address (e.g., hash value) of the unit of data. The storage system then determines, based on the content address, the physical location of the unit of data in the storage system, retrieves the unit of data from that location, and returns the unit of data to the host computer.
- If, in
step 220, a determination is made to not store the content in CAS, then theapplication server 130 may store the content locally in astorage system 135. The application server may also store metadata associated with the content locally on theapplication server 130 or in thestorage system 135. Further, the content and the metadata may be correlated. For example, the metadata may be stored in a database or an XML file and may include a pointer or reference to the content (such as a file location or unique database ID depending on the implementation and the type of data). The locally-stored metadata may later be searched and the content and metadata served to a searcher. Methods for choosing what data to store in CAS storage and what content to not store in CAS may include data types (e.g., PDF files, images, and medical records may be indicated as CAS candidates) last modification date, identity of the providing system, indications in the metadata, compliance with Sarbanes-Oxley, age of the file, status of a project related to the file, size of the file, or ways known to those skilled in the art. - If, in
step 220, a determination is made to store the content at aCAS server 110A-C, then the content is sent to a CAS server instep 230, a metadata file is created instep 240, and the content and metadata are associated with each other instep 250. In the depicted embodiment of the process, the application server may send the content to the CAS server instep 230 and the CAS server may create the metadata file instep 240. In other embodiments, the metadata file is created at the application server and both are sent to the CAS server. Similarly, the metadata file may be associated with the content file (step 250) either at the application server or at the CAS server. In some embodiments, the application server may send the content and/or the metadata to more than one server. - The metadata corresponding to the CAS content may include any relevant data such as author, data owner, patient name (in the case of medical data), patient number, television episode title, creation date, etc. The metadata may be stored in a number of ways. For example, the data may be stored in an XML file, in an unformatted text file, in a formatted text file, in a database entry, or in any other of a myriad of appropriate manners. The metadata may come from a DICOM header, text in the file, analysis of the file (e.g., size and modification date of the file), summary or metadata fields in the document, descriptive or other files associated with received file, or other sources of metadata. This stored metadata may then later be searchable. Associating the metadata with the content in
step 250 may comprise including the GUID for the content in the metadata file or having a separate file, database entry, etc. that includes references to the metadata and the content. - In the depicted embodiments, in
step 260; the CAS content and metadata may be distributed to multiple CAS servers. The CAS content and metadata may be distributed to multiple servers simultaneously or sequentially, in a hierarchical fashion where each CAS server distributes the data to one or more other CAS servers, or in any other appropriate manner or topology. In other embodiments, as noted herein, the CAS content and metadata may not be distributed among CAS servers and step 260 may not be performed. In some embodiments, distributing the CAS content and the metadata can provide for redundancy benefits and/or communication benefits (given that, as the result of distribution, the CAS content may be replicated at a location that is close on the network). - In some embodiments, a CAS server may be configured to replicate CAS objects. It may be useful to distribute the CAS content across multiple CAS servers for redundancy or other reasons. Depending on embodiment and other factors, a CAS server may replicate objects once it receives them, after a particular request for replications, during some preconfigured interval, or for any other appropriate reason.
FIG. 3 is a block diagram of an exemplary process for replicating objects and metadata. - In
step 310, a CAS server that has content to be replicated sends that content and the associated metadata to another CAS server. This can be accomplished, for example, usingnetwork 101. The metadata may be embedded within, appended to, or separate from the content. - In
step 320, the content and metadata are received by the receiving CAS server and, instep 330, are parsed. After the data has been parsed, it is stored into a database in step 340. How the metadata is parsed will depend on the embodiment and how the data is formatted. For example, if the metadata is in an XML file, then the XML file may be parsed based on the known format of the file and stored, in step 340, into the metadata database. - In some embodiments, the metadata database may include separate fields for each of known element of metadata. For example, for a DICOM image, there are numerous known fields in the header, including patient name. The database that houses the metadata may have fields for these known elements of metadata. In some embodiments, the database may have one or more free text or other fields that will allow for storage of unknown or uncategorized metadata, such as a “notes” section of a patient chart or a “description” section of a television episode. In some embodiments, all of the database fields may later be searchable jointly or separately.
- In some embodiments, the database that stores the metadata may be replicated, distributed, or otherwise available to multiple CAS servers and multiple application servers (such as those depicted in
FIG. 1 ). Each CAS server may have its own database and the metadata for the content stored at that CAS server is stored therein. In some embodiments, a CAS server's database may also have metadata and information on finding associated CAS content for things that are stored at other CAS servers, even if that content is not also stored at that CAS server. - The metadata may also be stored, in some embodiments, in storage other than a database. For example, the metadata may be stored in a flat file, multiple flat files, or any other storage mechanism or searchable storage mechanism.
- Once the content is stored on the CAS servers, then, as depicted in
FIG. 4 , data can be retrieved from the CAS storage.FIG. 4 depicts a block diagram of an exemplary process for retrieving CAS content from a CAS server. - In
step 410, a query is received, perhaps from a user using aclient system 140B. The query can be in SQL, a Boolean search string, a natural language search, or any other appropriate format. In this embodiment, in step 420, the search is sent to other CAS servers. For example, as depicted inFIG. 1 , after receiving a query from a user using aclient system 140B, aCAS server 110B may send the query toother CAS servers - In some embodiments, after the search is sent to the remote CAS servers in step 420, the search is performed locally in
step 430. The local search can then be compiled and sent to the requester immediately, or, as depicted, combined with any results received from remote CAS servers and then sent to the requester instep 450. In some embodiments, the local search is performed before or simultaneously with the forwarding of the query to other CAS servers. For example, in some embodiments, a local query is first made for a file and if the query is completely satisfied, then no query is distributed to the other CAS servers. - The local query performed in
step 430 can take any appropriate form and will depend on the embodiment and the format of the received query. For example, if the received query is an SQL query and the metadata is stored in a database, then the received SQL query or some modification thereof may be used to query the local data. If the received query is a Boolean search and the metadata is stored in a flat file, then a text search based on the Boolean query may be performed. Once matching metadata is found, then the associated CAS content is retrieved and made ready to send to the requester. - In
steps 440 and 450, the CAS server may await results from the other CAS servers. All of the received results are combined and forwarded instep 460. For example, if a CAS server storing DICOM images requested more results for a particular patient name and patient ID, then the DICOM CAS server may send the request to multiple CAS servers in order to get any results for that patent stored on any of the other servers. The results may be checked for validity via a checksum or other assurance mechanism built into the system, or any other appropriate CAS procedures. Corrupted or otherwise invalid files may be excluded from or flagged in the CAS or in the result set sent to the requester. - Given the nature of the redundancy and distribution that may be possible with embodiments herein, multiple copies of the same CAS data may be received from multiple CAS servers. In such cases, any duplicate files may be excluded from or flagged in the result set sent to the requester. Additionally, in some embodiments, if the remote CAS server does not send a response within a particular timeout period, the CAS server may no longer await results and may send out any received results in
step 450. - The results sent to the requester in
step 460 can take any appropriate form, including a single compressed file, a pointed to one or more accessible pieces of data that comprise the complete data set, or any other appropriate mechanism. -
FIG. 5 depicts a block diagram of an exemplary process for retrieving CAS data via an application server. The process depicted inFIG. 5 is similar to that depicted inFIG. 4 , except that the search is initiated first by a user to an application server. The application server then sends the request to multiple CAS servers. For example, a user using aclient system 140A sends a request for data to anapplication server 130, theapplication server 130 receives the request (step 510), theapplication server 130 forwards the request to theCAS servers 110A-C (step 520), the application server searches locally (step 530), and receives or times out waiting for results from the CAS servers (steps 540 and 550). Once all of the results are received and compiled as above, the results are sent to theclient system 140A (step 560). - The local search in
step 530 at the application server may be for CAS data, or it may be for other application data. For example, if theCAS servers 110A-C store DICOM images and theapplication server 130 stores patient demographic and billing information, then the local results may be related to the demographics and billing history of the results and the results from theCAS servers 110A-C may be DICOM images. - As above, the results from the CAS servers (and the application server if it stores replicated data) may be checked not only for integrity (via checksums, e.g.), but also for duplicates. The duplicate results may be flagged or omitted from the search results sent.
- The processes and systems described herein may be performed on or encompass various types of hardware, such as computer systems. In some embodiments, the computer systems such as the
client system 140A-C, theapplication server 130, and the contentaddressable storage systems 110A-C may include a bus or other communication mechanism for communicating information, and a processor coupled with the bus for processing information. The computer systems may have a main memory, such as a random access memory or other dynamic storage device, coupled to the bus. The main memory may be used to store instructions and temporary variables. The computer systems may also include a read-only memory or other static storage device coupled to the bus for storing static information and instructions. The computer systems may also be coupled to a display, such as a CRT or LCD monitor. Input devices may also be coupled to the computer system. These input devices may include a mouse, a trackball, or cursor direction keys. Each computer system may be implemented using one or more physical computers or computer systems or portions thereof. The instructions executed by the computer system may also be read in from a computer-readable medium. The computer-readable medium may be a CD, DVD, optical or magnetic disk, laserdisc, carrier wave, or any other medium that is readable by the computer system. In some embodiments, hardwired circuitry may be used in place of or in combination with software instructions executed by the processor. - As will be apparent, the features and attributes of the specific embodiments disclosed above may be combined in different ways to form additional embodiments, all of which fall within the scope of the present disclosure.
- Conditional language used herein, such as, among others, “can,” “could,” “might,” “may,” “e.g.,” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or states. Thus, such conditional language is not generally intended to imply that features, elements and/or states are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without author input or prompting, whether these features, elements and/or states are included or are to be performed in any particular embodiment.
- Any process descriptions, elements, or blocks in the flow diagrams described herein and/or depicted in the attached figures should be understood as potentially representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process. Alternate implementations are included within the scope of the embodiments described herein in which elements or functions may be deleted, executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those skilled in the art.
- All of the methods and processes described above may be embodied in, and fully automated via, software code modules executed by one or more general purpose computers or processors, such as those computer systems described above. The code modules may be stored in any type of computer-readable medium or other computer storage device. Some or all of the methods may alternatively be embodied in specialized computer hardware.
- It should be emphasized that many variations and modifications may be made to the above-described embodiments, the elements of which are to be understood as being among other acceptable examples. All such modifications and variations are intended to be included herein within the scope of this disclosure and protected by the following claims.
Claims (18)
1. A computer-implemented method for managing metadata in a content addressable storage system, comprising:
receiving a file for storage at a content addressable storage server, the file comprises a header and data, and wherein the content addressable storage server stores and retrieves the data based on content of the data rather than with a hierarchical file system;
automatically obtaining with one or more computer processors metadata associated with the data from the header of the file;
storing the metadata in a metadata storage device, wherein the metadata is stored in association with the data stored in the content addressable storage server;
receiving a query from a requester for content at the content addressable storage server;
searching the metadata storage device for content related to the received query; and
when the metadata associated with the file is indicated by the query:
retrieving the file stored in the content addressable storage; and
sending the retrieved file to the requester.
2. The method of claim 1 , wherein the method further comprises:
sending the query to a second content addressable storage server;
receiving one or more files related to the query from the second content addressable storage server; and
sending to the requester the retrieved file and the one or more files related to the query from the second content addressable storage server.
3. The method of claim 1 , wherein the method further comprises:
sending the query to a second content addressable storage server;
receiving one or more files related to the query from the second content addressable storage server; and
determining whether any of the retrieved file and the one or more files received from the second content addressable storage server are duplicates.
4. The method of claim 3 , wherein the method further comprises:
sending to the requester one or more files that are not duplicates.
5. The method of claim 1 , wherein the content addressable storage server stores DICOM images and the metadata is related to the DICOM images.
6. The method of claim 1 , wherein the method further comprises:
distributing the file and the metadata to a second content addressable storage server.
7. The method of claim 1 , wherein the method further comprises:
distributing the file and the metadata to a plurality of content addressable storage servers in a hierarchical fashion.
8. The method of claim 7 , wherein the method further comprises:
sending the query to the plurality of content addressable storage servers, based on the metadata;
receiving one or more files related to the query from the plurality of content addressable storage servers; and
sending to the requester the retrieved file and the one or more files related to the query from the plurality of content addressable storage servers.
9. A computer-implemented method for managing metadata 1D a content addressable storage system, comprising:
receiving one or more files for storage at a content addressable storage server, wherein each of the one or more files comprises a header and data, and wherein the content addressable storage server stores and retrieves the data based on content of the data rather than with a hierarchical file system;
automatically obtaining with one or more computer processors metadata associated with the data from the header of each of the one or more files;
storing the metadata in a metadata storage device, wherein the metadata is stored in association with the data stored in the content addressable storage server;
receiving a first query from a requester for content at an application server;
searching locally at the application server for one or more files related to the first query;
sending a second query, related to the first query, to the content addressable storage server;
receiving one or more files related to the second query from the content addressable storage server; and
sending to the requester the one or more files found locally based on the first query and the one or more files received from the content addressable storage server based on the second query.
10. The method of claim 9 , wherein the method further comprises:
determining whether any of the one or more files found locally based on the first query and the one or more files received from the content addressable storage server based on the second query are duplicates.
11. The method of claim 10 , wherein the method further comprises:
sending to the requester one or more files that are not duplicates.
12. The method of claim 9 , wherein the method further comprises:
sending the second query to a second content addressable storage server;
receiving one or more files related to the second query from the second content addressable storage server; and
sending to the requester the one or more files received from the second content addressable storage server based on the second query.
13. The method of claim 9 , wherein the content addressable storage server stores DICOM images and the metadata is related to the DICOM images.
14. A computer-implemented system for managing metadata in a content addressable storage system, comprising:
a content addressable storage system configured to:
receive a file for storage, said file to be stored using content addressable storage;
store metadata associated with the file in a storage mechanism for storing metadata for content addressable storage;
receive a query from a requester for content;
search the metadata storage mechanism for content related to the received query; and
when the metadata associated with the file is indicated by the query:
retrieve the file stored in the content addressable storage; and
send the retrieved file to the requester.
15. The system of claim 14 , wherein the content addressable storage system is further configured to:
send the query to a second content addressable storage system;
receive one or more files related to the query from the second content addressable storage system; and
send to the requester the retrieved file and the one or more files related to the query from the second content addressable storage system.
16. The system of claim 14 , wherein the content addressable storage system is further configured to:
send the query to a second content addressable storage system;
receive one or more files related to the query from the second content addressable storage system; and
determine whether any of the retrieved file and the one or more files received from the second content addressable storage system are duplicates.
17. The system of claim 16 , wherein the content addressable storage system is further configured to:
send to the requester one or more files that are not duplicates.
18. The system of claim 14 , wherein the content addressable storage system stores DICOM images and the metadata is related to the DICOM images.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US17/565,280 US20220197954A1 (en) | 2008-10-24 | 2021-12-29 | System and methods for metadata management in content addressable storage |
US18/131,320 US20240111812A1 (en) | 2008-10-24 | 2023-04-05 | System and methods for metadata management in content addressable storage |
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10834108P | 2008-10-24 | 2008-10-24 | |
US12/605,036 US8788519B2 (en) | 2008-10-24 | 2009-10-23 | System and methods for metadata management in content addressable storage |
US14/335,813 US20150106401A1 (en) | 2008-10-24 | 2014-07-18 | System and methods for metadata management in content addressable storage |
US15/331,775 US20170235850A1 (en) | 2008-10-24 | 2016-10-21 | System and methods for metadata management in content addressable storage |
US16/663,273 US20200125604A1 (en) | 2008-10-24 | 2019-10-24 | System and methods for metadata management in content addressable storage |
US17/565,280 US20220197954A1 (en) | 2008-10-24 | 2021-12-29 | System and methods for metadata management in content addressable storage |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/663,273 Continuation US20200125604A1 (en) | 2008-10-24 | 2019-10-24 | System and methods for metadata management in content addressable storage |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US18/131,320 Continuation US20240111812A1 (en) | 2008-10-24 | 2023-04-05 | System and methods for metadata management in content addressable storage |
Publications (1)
Publication Number | Publication Date |
---|---|
US20220197954A1 true US20220197954A1 (en) | 2022-06-23 |
Family
ID=42119704
Family Applications (6)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/605,036 Active 2030-07-24 US8788519B2 (en) | 2008-10-24 | 2009-10-23 | System and methods for metadata management in content addressable storage |
US14/335,813 Abandoned US20150106401A1 (en) | 2008-10-24 | 2014-07-18 | System and methods for metadata management in content addressable storage |
US15/331,775 Abandoned US20170235850A1 (en) | 2008-10-24 | 2016-10-21 | System and methods for metadata management in content addressable storage |
US16/663,273 Abandoned US20200125604A1 (en) | 2008-10-24 | 2019-10-24 | System and methods for metadata management in content addressable storage |
US17/565,280 Abandoned US20220197954A1 (en) | 2008-10-24 | 2021-12-29 | System and methods for metadata management in content addressable storage |
US18/131,320 Pending US20240111812A1 (en) | 2008-10-24 | 2023-04-05 | System and methods for metadata management in content addressable storage |
Family Applications Before (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/605,036 Active 2030-07-24 US8788519B2 (en) | 2008-10-24 | 2009-10-23 | System and methods for metadata management in content addressable storage |
US14/335,813 Abandoned US20150106401A1 (en) | 2008-10-24 | 2014-07-18 | System and methods for metadata management in content addressable storage |
US15/331,775 Abandoned US20170235850A1 (en) | 2008-10-24 | 2016-10-21 | System and methods for metadata management in content addressable storage |
US16/663,273 Abandoned US20200125604A1 (en) | 2008-10-24 | 2019-10-24 | System and methods for metadata management in content addressable storage |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US18/131,320 Pending US20240111812A1 (en) | 2008-10-24 | 2023-04-05 | System and methods for metadata management in content addressable storage |
Country Status (2)
Country | Link |
---|---|
US (6) | US8788519B2 (en) |
WO (1) | WO2010048531A1 (en) |
Families Citing this family (26)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020046061A1 (en) | 2000-02-11 | 2002-04-18 | Wright Kenneth L. | Personal information system |
US7933472B1 (en) | 2006-04-26 | 2011-04-26 | Datcard Systems, Inc. | System for remotely generating and distributing DICOM-compliant media volumes |
US9171344B2 (en) | 2007-10-30 | 2015-10-27 | Onemednet Corporation | Methods, systems, and devices for managing medical images and records |
US8065166B2 (en) | 2007-10-30 | 2011-11-22 | Onemednet Corporation | Methods, systems, and devices for managing medical images and records |
US9760677B2 (en) | 2009-04-29 | 2017-09-12 | Onemednet Corporation | Methods, systems, and devices for managing medical images and records |
US8756437B2 (en) | 2008-08-22 | 2014-06-17 | Datcard Systems, Inc. | System and method of encryption for DICOM volumes |
US8788519B2 (en) | 2008-10-24 | 2014-07-22 | John C. Canessa | System and methods for metadata management in content addressable storage |
US8407244B2 (en) | 2010-04-23 | 2013-03-26 | Datcard Systems, Inc. | Management of virtual packages of medical data in interconnected content-addressable storage systems |
WO2012078898A2 (en) | 2010-12-10 | 2012-06-14 | Datcard Systems, Inc. | Secure portable medical information access systems and methods related thereto |
CN102024059B (en) * | 2010-12-31 | 2012-07-18 | 成都市华为赛门铁克科技有限公司 | Method and device for protecting redundant array of independent disk in file system |
US9639591B2 (en) | 2011-06-13 | 2017-05-02 | EMC IP Holding Company LLC | Low latency replication techniques with content addressable storage |
US9383928B2 (en) * | 2011-06-13 | 2016-07-05 | Emc Corporation | Replication techniques with content addressable storage |
US20130067346A1 (en) * | 2011-09-09 | 2013-03-14 | Microsoft Corporation | Content User Experience |
US9258144B2 (en) * | 2012-02-23 | 2016-02-09 | Infosys Limited | Methods, systems and computer-readable media for integrating a composite MIME message |
CN103369002B (en) * | 2012-03-30 | 2018-03-27 | 腾讯科技(深圳)有限公司 | A kind of method and system of resource downloading |
US9298730B2 (en) | 2012-07-04 | 2016-03-29 | International Medical Solutions, Inc. | System and method for viewing medical images |
US9286323B2 (en) * | 2013-02-25 | 2016-03-15 | International Business Machines Corporation | Context-aware tagging for augmented reality environments |
US10360218B2 (en) * | 2013-09-30 | 2019-07-23 | Hyland Switzerland Sàrl | System and methods for caching and querying objects stored in multiple databases |
AU2015207840B2 (en) * | 2014-07-31 | 2020-06-18 | Samsung Electronics Co., Ltd. | System and method of managing metadata |
KR102322031B1 (en) * | 2014-07-31 | 2021-11-08 | 삼성전자주식회사 | System and method for managing metadata |
US11017014B2 (en) * | 2015-05-22 | 2021-05-25 | Box, Inc. | Using shared metadata to preserve logical associations between files when the files are physically stored in dynamically-determined cloud-based storage structures |
WO2018006399A1 (en) * | 2016-07-08 | 2018-01-11 | SZ DJI Technology Co., Ltd. | Method and system for combining and editing uav operation data and video data |
US10938950B2 (en) * | 2017-11-14 | 2021-03-02 | General Electric Company | Hierarchical data exchange management system |
US10585750B2 (en) | 2017-12-01 | 2020-03-10 | International Business Machines Corporation | Slice-embedded object metadata |
CN109598518A (en) * | 2018-09-30 | 2019-04-09 | 阿里巴巴集团控股有限公司 | Method for anti-counterfeit and device, electronic equipment based on block chain |
US11922074B1 (en) | 2020-10-11 | 2024-03-05 | Edjx, Inc. | Systems and methods for a content-addressable peer-to-peer storage network |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050097260A1 (en) * | 2003-11-03 | 2005-05-05 | Mcgovern William P. | System and method for record retention date in a write once read many storage system |
US20070050415A1 (en) * | 2005-08-26 | 2007-03-01 | Emc Corporation | Methods and apparatus for scheduling an action on a computer |
US20080065718A1 (en) * | 2006-09-12 | 2008-03-13 | Emc Corporation | Configuring a cache prefetch policy that is controllable based on individual requests |
Family Cites Families (243)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US1234567A (en) * | 1915-09-14 | 1917-07-24 | Edward J Quigley | Soft collar. |
US4055851A (en) | 1976-02-13 | 1977-10-25 | Digital Equipment Corporation | Memory module with means for generating a control signal that inhibits a subsequent overlapped memory cycle during a reading operation portion of a reading memory cycle |
US4386233A (en) | 1980-09-29 | 1983-05-31 | Smid Miles E | Crytographic key notarization methods and apparatus |
NL8101667A (en) | 1981-04-03 | 1982-11-01 | Philips Nv | RADIATION EXAMINATION DEVICE WITH FILM MEMORY. |
US4491725A (en) | 1982-09-29 | 1985-01-01 | Pritchard Lawrence E | Medical insurance verification and processing system |
US4860112A (en) | 1984-06-07 | 1989-08-22 | Raytel Systems Corporation | Teleradiology system having multiple compressor/expanders |
US4874935A (en) | 1986-03-10 | 1989-10-17 | Data Card Coprporation | Smart card apparatus and method of programming same |
DE3722075A1 (en) | 1986-07-02 | 1988-03-17 | Toshiba Kawasaki Kk | Image diagnostics system |
US5019975A (en) | 1986-08-08 | 1991-05-28 | Fuji Photo Film Co., Ltd. | Method for constructing a data base in a medical image control system |
US4945410A (en) | 1987-02-09 | 1990-07-31 | Professional Satellite Imaging, Inc. | Satellite communications system for medical related images |
US5005126A (en) | 1987-04-09 | 1991-04-02 | Prevail, Inc. | System and method for remote presentation of diagnostic image information |
US4958283A (en) | 1987-07-08 | 1990-09-18 | Kabushiki Kaisha Toshiba | Method and system for storing and communicating medical image data |
DE68914720T2 (en) | 1988-05-31 | 1994-11-03 | Sharp Kk | Outpatient electrocardiography device. |
US5319629A (en) | 1988-08-25 | 1994-06-07 | Sparta, Inc. | Content addressable optical data storage system |
US4852570A (en) | 1989-02-09 | 1989-08-01 | Levine Alfred B | Comparative medical-physical analysis |
JPH02132366U (en) | 1989-04-03 | 1990-11-02 | ||
JPH03149614A (en) | 1989-08-31 | 1991-06-26 | Univ California | Information processing system and memory processing |
US5272625A (en) | 1990-05-17 | 1993-12-21 | Kabushiki Kaisha Toshiba | Medical image data managing system |
US5822544A (en) | 1990-07-27 | 1998-10-13 | Executone Information Systems, Inc. | Patient care and communication system |
US5291399A (en) | 1990-07-27 | 1994-03-01 | Executone Information Systems, Inc. | Method and apparatus for accessing a portable personal database as for a hospital environment |
EP0481735A3 (en) | 1990-10-19 | 1993-01-13 | Array Technology Corporation | Address protection circuit |
US5321681A (en) | 1990-11-21 | 1994-06-14 | Image Premastering Services, Ltd. | Apparatus for recording, storing and electronically accessing images |
DE69131681T2 (en) | 1990-11-22 | 2000-06-08 | Toshiba Kawasaki Kk | Computerized diagnostic system for medical use |
JP3382978B2 (en) | 1991-10-16 | 2003-03-04 | 東芝医用システムエンジニアリング株式会社 | Medical data storage system and control method thereof |
JP3071929B2 (en) | 1992-02-21 | 2000-07-31 | 株式会社東芝 | Medical support system and medical support method |
US5544649A (en) | 1992-03-25 | 1996-08-13 | Cardiomedix, Inc. | Ambulatory patient health monitoring techniques utilizing interactive visual communication |
US5319543A (en) | 1992-06-19 | 1994-06-07 | First Data Health Services Corporation | Workflow server for medical records imaging and tracking system |
JP3237900B2 (en) | 1992-06-19 | 2001-12-10 | 株式会社東芝 | Image display system |
US5321520A (en) | 1992-07-20 | 1994-06-14 | Automated Medical Access Corporation | Automated high definition/resolution image storage, retrieval and transmission system |
US6283761B1 (en) | 1992-09-08 | 2001-09-04 | Raymond Anthony Joao | Apparatus and method for processing and/or for providing healthcare information and/or healthcare-related information |
US5734915A (en) | 1992-11-25 | 1998-03-31 | Eastman Kodak Company | Method and apparatus for composing digital medical imagery |
US5848198A (en) | 1993-10-08 | 1998-12-08 | Penn; Alan Irvin | Method of and apparatus for analyzing images and deriving binary image representations |
US5469353A (en) | 1993-11-26 | 1995-11-21 | Access Radiology Corp. | Radiological image interpretation apparatus and method |
AU1294995A (en) | 1993-11-29 | 1995-06-19 | Perception, Inc. | Pc based ultrasound device with virtual control user interface |
US6022315A (en) | 1993-12-29 | 2000-02-08 | First Opinion Corporation | Computerized medical diagnostic and treatment advice system including network access |
WO1995019030A1 (en) | 1994-01-05 | 1995-07-13 | Pois, Inc. | Apparatus and method for a personal onboard information system |
US5531227A (en) | 1994-01-28 | 1996-07-02 | Schneider Medical Technologies, Inc. | Imaging device and method |
US5559888A (en) | 1994-02-15 | 1996-09-24 | Lucent Technologies Inc. | Secure information retrieval service (SIRS) |
CA2125300C (en) | 1994-05-11 | 1999-10-12 | Douglas J. Ballantyne | Method and apparatus for the electronic distribution of medical information and patient services |
EP0684565A1 (en) | 1994-05-27 | 1995-11-29 | Eastman Kodak Company | Medical image archiving of lossy and lossless images on a recordable CD |
US5724582A (en) | 1994-05-27 | 1998-03-03 | Eastman Kodak Company | Medical image archiving with lossy images on two or more recordable CDs |
US5590038A (en) | 1994-06-20 | 1996-12-31 | Pitroda; Satyan G. | Universal electronic transaction card including receipt storage and system and methods of conducting electronic transactions |
US5451763A (en) | 1994-07-05 | 1995-09-19 | Alto Corporation | Personal medical IC card and read/write unit |
US5995077A (en) | 1994-07-20 | 1999-11-30 | The United States Of America As Represented By The Secretary Of The Navy | Portable, wearable read/write data device |
US5579296A (en) | 1995-01-18 | 1996-11-26 | Cyberwerks Interactive, L.L.C. | Optically readable thin film digital data storage medium |
US5499293A (en) | 1995-01-24 | 1996-03-12 | University Of Maryland | Privacy protected information medium using a data compression method |
US5542768A (en) | 1995-02-03 | 1996-08-06 | Rimage Corporation | Apparatus for printing on plastic disk |
US5740428A (en) | 1995-02-07 | 1998-04-14 | Merge Technologies, Inc. | Computer based multimedia medical database management system and user interface |
US5659741A (en) | 1995-03-29 | 1997-08-19 | Stuart S. Bowie | Computer system and method for storing medical histories using a carrying size card |
US5668998A (en) | 1995-04-26 | 1997-09-16 | Eastman Kodak Company | Application framework of objects for the provision of DICOM services |
US6035280A (en) | 1995-06-16 | 2000-03-07 | Christensen; Scott N. | Electronic discount couponing method and apparatus for generating an electronic list of coupons |
JP3455790B2 (en) | 1995-06-30 | 2003-10-14 | 富士通株式会社 | Know-how management device used for information retrieval |
JPH09128408A (en) | 1995-08-25 | 1997-05-16 | Hitachi Ltd | Media for interactive recording and reproducing and reproducing device |
US5899998A (en) | 1995-08-31 | 1999-05-04 | Medcard Systems, Inc. | Method and system for maintaining and updating computerized medical records |
US5597182A (en) | 1995-09-26 | 1997-01-28 | Motorola, Inc. | Personal human anatomy card and methods and systems for producing same |
US5949491A (en) | 1995-10-24 | 1999-09-07 | Dicomit Imaging Systems Corp. | Ultrasound image management system |
US5597995A (en) | 1995-11-08 | 1997-01-28 | Automated Prescription Systems, Inc. | Automated medical prescription fulfillment system having work stations for imaging, filling, and checking the dispensed drug product |
JP3493847B2 (en) | 1995-11-15 | 2004-02-03 | 株式会社日立製作所 | Wide-area medical information system |
WO1997018942A1 (en) | 1995-11-22 | 1997-05-29 | Astral L.L.C. | Method and apparatus for manufacturing compact discs having a non-round outer profile |
US6067075A (en) | 1995-12-21 | 2000-05-23 | Eastman Kodak Company | Controller for medical image review station |
US5734629A (en) | 1995-12-28 | 1998-03-31 | Rimage Corporation | CD transporter |
US5809243A (en) | 1995-12-29 | 1998-09-15 | Lsi Logi Corporation | Personal interface system for wireless and wired communications |
US5671353A (en) | 1996-02-16 | 1997-09-23 | Eastman Kodak Company | Method for validating a digital imaging communication standard message |
US5721825A (en) * | 1996-03-15 | 1998-02-24 | Netvision, Inc. | System and method for global event notification and delivery in a distributed computing environment |
US6973034B1 (en) | 1999-06-29 | 2005-12-06 | Cisco Technology, Inc. | Technique for collecting operating information from network elements, and for controlling network element behavior in a feedback-based, adaptive data network |
US6006191A (en) | 1996-05-13 | 1999-12-21 | Dirienzo; Andrew L. | Remote access medical image exchange system and methods of operation therefor |
US5763862A (en) | 1996-06-24 | 1998-06-09 | Motorola, Inc. | Dual card smart card reader |
US5823948A (en) | 1996-07-08 | 1998-10-20 | Rlis, Inc. | Medical records, documentation, tracking and order entry system |
US5687717A (en) | 1996-08-06 | 1997-11-18 | Tremont Medical, Inc. | Patient monitoring system with chassis mounted or remotely operable modules and portable computer |
US5796862A (en) | 1996-08-16 | 1998-08-18 | Eastman Kodak Company | Apparatus and method for identification of tissue regions in digital mammographic images |
US5867795A (en) | 1996-08-23 | 1999-02-02 | Motorola, Inc. | Portable electronic device with transceiver and visual image display |
JP3688822B2 (en) | 1996-09-03 | 2005-08-31 | 株式会社東芝 | Electronic medical record system |
US5924074A (en) | 1996-09-27 | 1999-07-13 | Azron Incorporated | Electronic medical records system |
US5946276A (en) | 1996-11-15 | 1999-08-31 | Rimage Corporation | Data flow management system for recordable media |
US5995965A (en) | 1996-11-18 | 1999-11-30 | Humetrix, Inc. | System and method for remotely accessing user data records |
US5873824A (en) | 1996-11-29 | 1999-02-23 | Arch Development Corporation | Apparatus and method for computerized analysis of interstitial infiltrates in chest images using artificial neural networks |
US6131090A (en) | 1997-03-04 | 2000-10-10 | Pitney Bowes Inc. | Method and system for providing controlled access to information stored on a portable recording medium |
US6148331A (en) | 1997-04-25 | 2000-11-14 | Parry; Rhys Evan | Destination website access and information gathering system |
US6082776A (en) | 1997-05-07 | 2000-07-04 | Feinberg; Lawrence E. | Storing personal medical information |
US5982736A (en) | 1997-05-15 | 1999-11-09 | Pierson; Gerald A. | Trading card optical compact disc and methods of using and forming same |
US6021404A (en) | 1997-08-18 | 2000-02-01 | Moukheibir; Nabil W. | Universal computer assisted diagnosis |
US5995345A (en) | 1997-11-18 | 1999-11-30 | Overbo; David M. | Data storage cartridge and adapter |
US6032120A (en) | 1997-12-16 | 2000-02-29 | Acuson Corporation | Accessing stored ultrasound images and other digital medical images |
US6014629A (en) | 1998-01-13 | 2000-01-11 | Moore U.S.A. Inc. | Personalized health care provider directory |
US6807632B1 (en) | 1999-01-21 | 2004-10-19 | Emc Corporation | Content addressable information encapsulation, representation, and transfer |
DE19802572A1 (en) | 1998-01-23 | 1999-08-05 | Siemens Health Service Gmbh & | Medical system architecture |
US6421650B1 (en) | 1998-03-04 | 2002-07-16 | Goetech Llc | Medication monitoring system and apparatus |
US6564256B1 (en) | 1998-03-31 | 2003-05-13 | Fuji Photo Film Co., Ltd. | Image transfer system |
AU3748699A (en) | 1998-04-15 | 1999-11-01 | Cyberhealth, Inc. | Visit verification method and system |
EP0952726B1 (en) | 1998-04-24 | 2003-06-25 | Eastman Kodak Company | Method and system for associating exposed radiographic films with proper patient information |
US6278999B1 (en) | 1998-06-12 | 2001-08-21 | Terry R. Knapp | Information management system for personal health digitizers |
US6260021B1 (en) | 1998-06-12 | 2001-07-10 | Philips Electronics North America Corporation | Computer-based medical image distribution system and method |
US6149440A (en) | 1998-09-18 | 2000-11-21 | Wyngate, Inc. | Methods and apparatus for authenticating informed consent |
US20050240445A1 (en) | 1998-09-29 | 2005-10-27 | Michael Sutherland | Medical archive library and method |
US6954802B2 (en) | 1998-09-29 | 2005-10-11 | Tdk Electronics Corporation | Removable media recording station for the medical industry |
US6363392B1 (en) | 1998-10-16 | 2002-03-26 | Vicinity Corporation | Method and system for providing a web-sharable personal database |
US5942165A (en) | 1998-10-20 | 1999-08-24 | Soundshape, Inc. | Method for making irregular shaped CD's and other playing discs |
US6466949B2 (en) * | 1998-11-23 | 2002-10-15 | Myway.Com Corporation | Performing event notification in a database having a distributed web cluster |
US6424996B1 (en) | 1998-11-25 | 2002-07-23 | Nexsys Electronics, Inc. | Medical network system and method for transfer of information |
US7283857B1 (en) | 1998-11-30 | 2007-10-16 | Hologic, Inc. | DICOM compliant file communication including quantitative and image data |
US20050086082A1 (en) | 1999-01-21 | 2005-04-21 | Patient Care Technologies | Portable health assistant |
US6654724B1 (en) | 1999-02-12 | 2003-11-25 | Adheris, Inc. | System for processing pharmaceutical data while maintaining patient confidentially |
US6954767B1 (en) | 1999-03-31 | 2005-10-11 | Fuji Photo Film Co., Ltd. | Server and method for searching for image using image prefetch, designating database and storage devices for searching, and setting retrieval and processing parameters for search |
US7177939B2 (en) | 1999-05-14 | 2007-02-13 | Cingular Wireless Ii, Llc | Aircraft data communications services for users |
US6539427B1 (en) | 1999-06-29 | 2003-03-25 | Cisco Technology, Inc. | Dynamically adaptive network element in a feedback-based data network |
US6584502B1 (en) | 1999-06-29 | 2003-06-24 | Cisco Technology, Inc. | Technique for providing automatic event notification of changing network conditions to network elements in an adaptive, feedback-based data network |
US6976165B1 (en) | 1999-09-07 | 2005-12-13 | Emc Corporation | System and method for secure storage, transfer and retrieval of content addressable information |
US6454705B1 (en) | 1999-09-21 | 2002-09-24 | Cardiocom | Medical wellness parameters management system, apparatus and method |
US7010701B1 (en) | 1999-10-19 | 2006-03-07 | Sbc Properties, L.P. | Network arrangement for smart card applications |
US20040078236A1 (en) | 1999-10-30 | 2004-04-22 | Medtamic Holdings | Storage and access of aggregate patient data for analysis |
US6574742B1 (en) | 1999-11-12 | 2003-06-03 | Insite One, Llc | Method for storing and accessing digital medical images |
US6155409A (en) | 1999-11-19 | 2000-12-05 | Hettinger; Gary F. | Personal emergency information and medication holder |
US6671714B1 (en) | 1999-11-23 | 2003-12-30 | Frank Michael Weyer | Method, apparatus and business system for online communications with online and offline recipients |
US6633674B1 (en) | 1999-11-24 | 2003-10-14 | General Electric Company | Picture archiving and communication system employing improved data compression |
US20020103675A1 (en) | 1999-11-29 | 2002-08-01 | John Vanelli | Apparatus and method for providing consolidated medical information |
US20030004760A1 (en) | 1999-12-03 | 2003-01-02 | Schiff Martin R. | Systems and methods of on-line booking of cruises |
US6397224B1 (en) | 1999-12-10 | 2002-05-28 | Gordon W. Romney | Anonymously linking a plurality of data records |
US6675271B1 (en) | 1999-12-16 | 2004-01-06 | General Electric Company | PACS archive techniques |
AU2001234835A1 (en) | 2000-02-09 | 2001-08-20 | Ernest W. Kinchen | Method and system for managing patient medical records |
US7302164B2 (en) | 2000-02-11 | 2007-11-27 | Datcard Systems, Inc. | System and method for producing medical image data onto portable digital recording media |
BR0108476A (en) | 2000-02-11 | 2003-04-22 | Marcio Marc Abreu | System and method for communicating product recall information, product-related warnings, or other information related to product users. |
US20020046061A1 (en) | 2000-02-11 | 2002-04-18 | Wright Kenneth L. | Personal information system |
US20010027402A1 (en) | 2000-02-14 | 2001-10-04 | Ramsaroop Peter R. | Method and apparatus for effectuating bilateral, consumer-driven healthcare commerce |
AU2001240087A1 (en) | 2000-03-10 | 2001-09-24 | Intehealth Incorporated | System and method for interacting with legacy healthcare database systems |
EP1297478A2 (en) | 2000-03-15 | 2003-04-02 | Emedicalfiles, Inc. | Web-hosted healthcare medical information management system |
US7965408B2 (en) | 2000-05-19 | 2011-06-21 | Cyrus Kurosh Samari | Medical data recording system |
US6678703B2 (en) | 2000-06-22 | 2004-01-13 | Radvault, Inc. | Medical image management system and method |
WO2002005061A2 (en) | 2000-07-06 | 2002-01-17 | David Paul Felsher | Information record infrastructure, system and method |
US7174362B1 (en) | 2000-11-21 | 2007-02-06 | Sungil Lee | Method and system for supplying products from pre-stored digital data in response to demands transmitted via computer network |
US20020077861A1 (en) | 2000-12-20 | 2002-06-20 | Hogan James K. | Compact disk based medical information system |
US6934698B2 (en) | 2000-12-20 | 2005-08-23 | Heart Imaging Technologies Llc | Medical image management system |
US7266556B1 (en) * | 2000-12-29 | 2007-09-04 | Intel Corporation | Failover architecture for a distributed storage system |
US6938206B2 (en) | 2001-01-19 | 2005-08-30 | Transolutions, Inc. | System and method for creating a clinical resume |
US20020103811A1 (en) | 2001-01-26 | 2002-08-01 | Fankhauser Karl Erich | Method and apparatus for locating and exchanging clinical information |
KR100392331B1 (en) | 2001-02-02 | 2003-07-22 | 서오텔레콤(주) | System for managing medical insurance using information communication network and method therefore |
US7386462B2 (en) | 2001-03-16 | 2008-06-10 | Ge Medical Systems Global Technology Company, Llc | Integration of radiology information into an application service provider DICOM image archive and/or web based viewer |
AU2002259081A1 (en) * | 2001-05-01 | 2002-11-11 | Amicas, Inc. | System and method for repository storage of private data on a network for direct client access |
US20030208382A1 (en) | 2001-07-05 | 2003-11-06 | Westfall Mark D | Electronic medical record system and method |
DE10140729A1 (en) | 2001-08-27 | 2002-07-25 | Christian Nehammer | Individual health ID card system based on CD-RW data medium on which patient records are stored together with computer programs to connect to a central computer for data exchange and updating |
AU2002363488A1 (en) | 2001-11-08 | 2003-05-19 | Amos Grushka | Portable personal health information package |
WO2003046827A1 (en) | 2001-11-22 | 2003-06-05 | Medecard Limited | Portable storage device for storing and accessing personal data |
JP2003202929A (en) | 2002-01-08 | 2003-07-18 | Ntt Docomo Inc | Distribution method and distribution system |
JP2003224674A (en) | 2002-01-30 | 2003-08-08 | Nec Infrontia Corp | Health management service system by portable telephone terminal |
US20100174750A1 (en) | 2002-03-19 | 2010-07-08 | Donovan Mark C | System and method for storing information for a wireless device |
US20030220822A1 (en) | 2002-05-22 | 2003-11-27 | Barry Fiala Enterprises I, Llc | Medical information registration and retrieval apparatus and method regular |
TW588243B (en) | 2002-07-31 | 2004-05-21 | Trek 2000 Int Ltd | System and method for authentication |
US7298836B2 (en) | 2002-09-24 | 2007-11-20 | At&T Bls Intellectual Property, Inc. | Network-based healthcare information systems |
US7047235B2 (en) | 2002-11-29 | 2006-05-16 | Agency For Science, Technology And Research | Method and apparatus for creating medical teaching files from image archives |
US20040146272A1 (en) | 2003-01-09 | 2004-07-29 | Kessel Kurt A. | System and method for managing video evidence |
US7437440B2 (en) | 2003-01-27 | 2008-10-14 | Microsoft Corporation | Peer-to-peer networking framework application programming interfaces |
US7802087B2 (en) | 2003-03-10 | 2010-09-21 | Igt | Universal method for submitting gaming machine source code software to a game certification laboratory |
US7089425B2 (en) | 2003-03-18 | 2006-08-08 | Ci4 Technologies, Inc. | Remote access authorization of local content |
US7596703B2 (en) | 2003-03-21 | 2009-09-29 | Hitachi, Ltd. | Hidden data backup and retrieval for a secure device |
US8819419B2 (en) | 2003-04-03 | 2014-08-26 | International Business Machines Corporation | Method and system for dynamic encryption of a URL |
EP1611693A4 (en) | 2003-04-10 | 2007-12-12 | Sk Telecom Co Ltd | A method and an apparatus for providing multimedia services in mobile terminal |
US8010717B2 (en) | 2003-04-17 | 2011-08-30 | Imetribus, Inc. | Method and system for communication and collaboration between a patient and healthcare professional |
US7426745B2 (en) | 2003-04-24 | 2008-09-16 | International Business Machines Corporation | Methods and systems for transparent data encryption and decryption |
US7836493B2 (en) | 2003-04-24 | 2010-11-16 | Attachmate Corporation | Proxy server security token authorization |
WO2005026893A2 (en) | 2003-09-05 | 2005-03-24 | Sensitech Inc. | Automated generation of reports reflecting statistical analyses of supply chain processes |
US7379605B1 (en) | 2003-09-09 | 2008-05-27 | Stelian Doru Ticsa | Method for the integration of medical imaging data and content for wireless transmission and remote viewing |
US20050075909A1 (en) | 2003-10-06 | 2005-04-07 | Geoffrey Flagstad | Medical record cards and storage systems |
US8457981B2 (en) | 2003-12-03 | 2013-06-04 | The Trizetto Group, Inc. | Bridged patient / provider centric method and system |
US20050125254A1 (en) | 2003-12-03 | 2005-06-09 | Roy Schoenberg | Key maintenance method and system |
US7444389B2 (en) * | 2003-12-09 | 2008-10-28 | Emc Corporation | Methods and apparatus for generating a content address to indicate data units written to a storage system proximate in time |
US7162571B2 (en) * | 2003-12-09 | 2007-01-09 | Emc Corporation | Methods and apparatus for parsing a content address to facilitate selection of a physical storage location in a data storage system |
US20060155584A1 (en) | 2003-12-12 | 2006-07-13 | Abhinav Aggarwal | System and Method for Patient Identification, Monitoring, Tracking, and Rescue |
US20050197859A1 (en) | 2004-01-16 | 2005-09-08 | Wilson James C. | Portable electronic data storage and retreival system for group data |
US7266566B1 (en) * | 2004-01-28 | 2007-09-04 | Breken Technologies Group | Database management system |
US20050192837A1 (en) | 2004-02-27 | 2005-09-01 | Cardiac Pacemakers, Inc. | Systems and methods for uploading and distributing medical data sets |
US7039628B2 (en) | 2004-04-21 | 2006-05-02 | Logan Jr Carmen | Portable health care history information system |
US7213022B2 (en) | 2004-04-29 | 2007-05-01 | Filenet Corporation | Enterprise content management network-attached system |
US7240150B1 (en) | 2004-04-30 | 2007-07-03 | Emc Corporation | Methods and apparatus for processing access requests in a content addressable computer system |
US7428611B1 (en) | 2004-04-30 | 2008-09-23 | Emc Corporation | Methods and apparatus for forwarding access requests in a content addressable computer system |
US7552356B1 (en) | 2004-06-30 | 2009-06-23 | Sun Microsystems, Inc. | Distributed data storage system for fixed content |
AU2005264608B2 (en) | 2004-07-22 | 2010-10-28 | Panasonic Corporation | Playback apparatus and playback method |
WO2006009221A1 (en) | 2004-07-22 | 2006-01-26 | Matsushita Electric Industrial Co., Ltd. | Reproduction device, reproduction method, program, and computer-readable recording medium |
US7657581B2 (en) | 2004-07-29 | 2010-02-02 | Archivas, Inc. | Metadata management for fixed content distributed data storage |
US7539813B1 (en) * | 2004-08-04 | 2009-05-26 | Emc Corporation | Methods and apparatus for segregating a content addressable computer system |
JP4541071B2 (en) * | 2004-08-25 | 2010-09-08 | カルソニックカンセイ株式会社 | Indicator and initialization drive |
US20060064328A1 (en) | 2004-08-30 | 2006-03-23 | Debarshi Datta | System and method for utilizing a DICOM structured report for workflow optimization |
US20060085226A1 (en) | 2004-10-14 | 2006-04-20 | Kamber Deirdre J | Emergency identification, medical treatment and records access authorization media |
US7865735B2 (en) | 2004-10-19 | 2011-01-04 | George Yiachos | Method and apparatus for managing personal medical information in a secure manner |
US7366836B1 (en) | 2004-12-23 | 2008-04-29 | Emc Corporation | Software system for providing storage system functionality |
KR20060081323A (en) | 2005-01-07 | 2006-07-12 | 엘지전자 주식회사 | Method and apparatus for reproducing a data recorded in recording medium using a local storage |
US20060155680A1 (en) | 2005-01-10 | 2006-07-13 | Peng Wu | Search file indicating languages associated with scenes |
KR101147763B1 (en) | 2005-01-19 | 2012-05-25 | 엘지전자 주식회사 | Data decryption method and apparatus, recoding medium comprising encrypted data |
US7434057B2 (en) | 2005-01-27 | 2008-10-07 | Hitachi, Ltd. | System and method for watermarking in accessed data in a storage system |
US20060242144A1 (en) * | 2005-03-24 | 2006-10-26 | Esham Matthew P | Medical image data processing system |
US7694331B2 (en) | 2005-04-01 | 2010-04-06 | Nokia Corporation | Phone with secure element and critical data |
US20070027715A1 (en) | 2005-06-13 | 2007-02-01 | Medcommons, Inc. | Private health information interchange and related systems, methods, and devices |
US8117045B2 (en) | 2005-09-12 | 2012-02-14 | Mymedicalrecords.Com, Inc. | Method and system for providing online medical records |
CA2623394A1 (en) | 2005-09-19 | 2007-03-29 | Industrial Color, Inc. | Digital file management |
US7860897B2 (en) | 2005-09-30 | 2010-12-28 | International Business Machines Corporation | Optimized method of locating complete aggregation of patient health records in a global domain |
US20070180509A1 (en) | 2005-12-07 | 2007-08-02 | Swartz Alon R | Practical platform for high risk applications |
US7734603B1 (en) | 2006-01-26 | 2010-06-08 | Netapp, Inc. | Content addressable storage array element |
US7747831B2 (en) | 2006-03-20 | 2010-06-29 | Emc Corporation | High efficiency portable archive and data protection using a virtualization layer |
US9137480B2 (en) | 2006-06-30 | 2015-09-15 | Cisco Technology, Inc. | Secure escrow and recovery of media device content keys |
US7974924B2 (en) | 2006-07-19 | 2011-07-05 | Mvisum, Inc. | Medical data encryption for communication over a vulnerable system |
US8381287B2 (en) | 2006-07-19 | 2013-02-19 | Secure Exchange Solutions, Llc | Trusted records using secure exchange |
US7546486B2 (en) | 2006-08-28 | 2009-06-09 | Bycast Inc. | Scalable distributed object management in a distributed fixed content storage system |
US7621445B2 (en) | 2006-09-12 | 2009-11-24 | International Business Machines Corporation | Method and apparatus for access to health data with portable media |
US20080071577A1 (en) | 2006-09-14 | 2008-03-20 | Highley Robert D | Dual-access security system for medical records |
US20080104099A1 (en) | 2006-10-31 | 2008-05-01 | Motorola, Inc. | Use of information correlation for relevant information |
US20080109250A1 (en) | 2006-11-03 | 2008-05-08 | Craig Allan Walker | System and method for creating and rendering DICOM structured clinical reporting via the internet |
US20080126729A1 (en) | 2006-11-28 | 2008-05-29 | Yigang Cai | Systems and methods for controlling access by a third party to a patient's medical records on a medical information card |
US7590672B2 (en) | 2006-12-11 | 2009-09-15 | Bycast Inc. | Identification of fixed content objects in a distributed fixed content storage system |
US8255382B2 (en) | 2007-06-20 | 2012-08-28 | Boopsie, Inc. | Dynamic menus for multi-prefix interactive mobile searches |
JP5145719B2 (en) * | 2007-01-30 | 2013-02-20 | ソニー株式会社 | Metadata collection system, content management server, metadata collection apparatus, metadata collection method and program |
WO2008099647A1 (en) | 2007-02-16 | 2008-08-21 | Panasonic Corporation | Reproducing apparatus |
US8131670B2 (en) * | 2007-02-22 | 2012-03-06 | Microsoft Corporation | Techniques to cross-synchronize data |
US8793704B2 (en) * | 2007-03-09 | 2014-07-29 | Microsoft Corporation | Techniques to manage event notifications |
US9996627B2 (en) | 2007-03-30 | 2018-06-12 | Excalibur Ip, Llc | Point of presence distribution mechanism for digital content objects |
US7877556B2 (en) | 2007-03-30 | 2011-01-25 | Hitachi, Ltd. | Method and apparatus for a unified storage system |
US20080274687A1 (en) | 2007-05-02 | 2008-11-06 | Roberts Dale T | Dynamic mixed media package |
WO2008137939A2 (en) | 2007-05-07 | 2008-11-13 | Archivas, Inc. | Method for data privacy in a fixed content distributed data storage |
US8626741B2 (en) | 2007-06-15 | 2014-01-07 | Emc Corporation | Process for cataloging data objects backed up from a content addressed storage system |
US20080319798A1 (en) | 2007-06-20 | 2008-12-25 | Kelley James M | Personalized medical information card and method for managing same |
US7783608B2 (en) | 2007-08-09 | 2010-08-24 | Hitachi, Ltd. | Method and apparatus for NAS/CAS integrated storage system |
US9154846B2 (en) | 2007-09-10 | 2015-10-06 | Verizon Patent And Licensing Inc. | Coordinated multi-media playback |
US7870154B2 (en) | 2007-09-28 | 2011-01-11 | Hitachi, Ltd. | Method and apparatus for NAS/CAS unified storage system |
US8881254B2 (en) | 2007-11-02 | 2014-11-04 | Magtek, Inc. | Method and system for managing virtual objects in a network |
US8635611B2 (en) | 2007-11-16 | 2014-01-21 | Microsoft Corporation | Creating virtual applications |
US7861049B2 (en) | 2007-11-19 | 2010-12-28 | Hitachi, Ltd. | Methods and apparatus for archiving digital data |
US20090157987A1 (en) * | 2007-12-14 | 2009-06-18 | Casdex, Inc. | System and Method for Creating Self-Authenticating Documents Including Unique Content Identifiers |
CN101903952B (en) | 2007-12-17 | 2012-08-22 | 松下电器产业株式会社 | Recording medium, recording device, and playback device for use in individual sales and method therefor |
US20090198515A1 (en) | 2008-02-05 | 2009-08-06 | Sawhney Amrita G | Organization method and system for health information |
US20090204433A1 (en) | 2008-02-11 | 2009-08-13 | Darian Garo B | Method for writing medical prescriptions, storing, and accessing patient medical records with improved portability and improved patient data security using a USB dongle device |
US8353012B2 (en) | 2008-02-26 | 2013-01-08 | Alejandro Emilio Del Real | Internet-based group website technology for content management and exchange (system and methods) |
US8872940B2 (en) | 2008-03-03 | 2014-10-28 | Videoiq, Inc. | Content aware storage of video data |
US8959199B2 (en) | 2008-03-18 | 2015-02-17 | Reduxio Systems Ltd. | Network storage system for a download intensive environment |
US20090319736A1 (en) | 2008-06-24 | 2009-12-24 | Hitachi, Ltd. | Method and apparatus for integrated nas and cas data backup |
US8271974B2 (en) | 2008-10-08 | 2012-09-18 | Kaavo Inc. | Cloud computing lifecycle management for N-tier applications |
US8788519B2 (en) | 2008-10-24 | 2014-07-22 | John C. Canessa | System and methods for metadata management in content addressable storage |
US8412539B2 (en) | 2009-04-09 | 2013-04-02 | Rajagopal Srinivasan | Handheld medical information management device |
US8433749B2 (en) | 2009-04-15 | 2013-04-30 | Accenture Global Services Limited | Method and system for client-side scaling of web server farm architectures in a cloud data center |
US20110004588A1 (en) | 2009-05-11 | 2011-01-06 | iMedix Inc. | Method for enhancing the performance of a medical search engine based on semantic analysis and user feedback |
US20100293524A1 (en) | 2009-05-12 | 2010-11-18 | International Business Machines, Corporation | Development environment for managing database aware software projects |
US8751495B2 (en) | 2009-09-29 | 2014-06-10 | Siemens Medical Solutions Usa, Inc. | Automated patient/document identification and categorization for medical data |
US20110112850A1 (en) | 2009-11-09 | 2011-05-12 | Roberto Beraja | Medical decision system including medical observation locking and associated methods |
US10514940B2 (en) | 2010-03-17 | 2019-12-24 | Microsoft Technology Licensing, Llc | Virtual application package reconstruction |
JP5551245B2 (en) | 2010-03-19 | 2014-07-16 | 株式会社日立製作所 | File sharing system, file processing method, and program |
US20110246307A1 (en) | 2010-03-31 | 2011-10-06 | Martin Zinkevich | Mass-Based Approach for Serving Impressions in Guaranteed Delivery Advertising |
US8842966B2 (en) | 2011-11-22 | 2014-09-23 | Virtual Imaging, Inc. | Apparatus and method for recording medical image data with embedded viewer in removable storage media |
-
2009
- 2009-10-23 US US12/605,036 patent/US8788519B2/en active Active
- 2009-10-23 WO PCT/US2009/061890 patent/WO2010048531A1/en active Application Filing
-
2014
- 2014-07-18 US US14/335,813 patent/US20150106401A1/en not_active Abandoned
-
2016
- 2016-10-21 US US15/331,775 patent/US20170235850A1/en not_active Abandoned
-
2019
- 2019-10-24 US US16/663,273 patent/US20200125604A1/en not_active Abandoned
-
2021
- 2021-12-29 US US17/565,280 patent/US20220197954A1/en not_active Abandoned
-
2023
- 2023-04-05 US US18/131,320 patent/US20240111812A1/en active Pending
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050097260A1 (en) * | 2003-11-03 | 2005-05-05 | Mcgovern William P. | System and method for record retention date in a write once read many storage system |
US20070050415A1 (en) * | 2005-08-26 | 2007-03-01 | Emc Corporation | Methods and apparatus for scheduling an action on a computer |
US20080065718A1 (en) * | 2006-09-12 | 2008-03-13 | Emc Corporation | Configuring a cache prefetch policy that is controllable based on individual requests |
Also Published As
Publication number | Publication date |
---|---|
US20100138446A1 (en) | 2010-06-03 |
US20240111812A1 (en) | 2024-04-04 |
US20170235850A1 (en) | 2017-08-17 |
US20200125604A1 (en) | 2020-04-23 |
WO2010048531A1 (en) | 2010-04-29 |
US20150106401A1 (en) | 2015-04-16 |
US8788519B2 (en) | 2014-07-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20240111812A1 (en) | System and methods for metadata management in content addressable storage | |
US20230091925A1 (en) | Event notification in interconnected content-addressable storage systems | |
US8843454B2 (en) | Elimination of duplicate objects in storage clusters | |
US7228299B1 (en) | System and method for performing file lookups based on tags | |
JP6448555B2 (en) | Content class for object storage indexing system | |
US9639542B2 (en) | Dynamic mapping of extensible datasets to relational database schemas | |
KR101127304B1 (en) | Hsm two-way orphan reconciliation for extremely large file systems | |
US20030106017A1 (en) | Computer-implemented PDF document management | |
US7991797B2 (en) | ID persistence through normalization | |
US10997037B1 (en) | Method and system for enhanced backup database indexing | |
JP2004295870A (en) | Consistency unit replication in application-defined system | |
US20130218843A1 (en) | Intelligent data archiving | |
US8311982B2 (en) | Storing update data using a processing pipeline | |
US9766949B2 (en) | System and method for locking exclusive access to a divided resource | |
US20110320416A1 (en) | Eliminating Redundant Processing of Data in Plural Node Systems | |
CN108256019A (en) | Database key generation method, device, equipment and its storage medium | |
CN115623008B (en) | Index construction method and system of Kubernetes resources | |
CN114238214A (en) | Intelligent financial archive storage management system and system | |
Huang et al. | InfoMall: A Large-Scale Storage System for Web Archiving | |
Keeton et al. | Automated SQL query generation for file search operations in a scale out file system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |