Granted Patent B2

US 12,299,166 · App. 17/870,317 · Granted May 13, 2025

Inventors: Andrew J. Witchger, Jr. (Durham, NC); Robert C. Williams (Durham, NC); Alexander E. Salmon (Garner, NC); Maureen E. Tuffnell (Wauwatosa, WI); Taylor M. Szeto (Cary, NC); Tammy B. Carrea (Raleigh, NC); Eric L. Buckland (Hickory, NC)

Assignee: Translational Imaging Innovations, Inc.

G06F21/6245G06F16/258G16H30/20G16H30/40

Abstract

Claims (37)

1. An application programming interface (API) resident on a computer that, upon receiving a message that a data set associated with an encounter experienced by a subject is available, causes a processor to:

read a structured file associated with the data set, the structured file having a set of records assigned to a subset of pre-defined fields and a location of one or more unstructured objects, the pre-defined fields being organized according to an ontology having at least records related to the subject, the encounter and the data set; and

populate at least first and second independent and distinct relational databases using endpoints of the API, the first relational database including records related to the one or more unstructured objects and excluding records associated with the subject and the encounter and the second relational database including records associated with the subject and the encounter,

wherein a schema of the second relational database includes at least a first addressable table that includes protected data associated with the subject and the encounter and at least a second addressable table that excludes protected data associated with the subject and the encounter;

wherein a set of addressable processes of the API are invoked to export one or more of:

unstructured objects and structured data about objects from the first relational database, the structured data being completely absent of records associated with the subject and the encounter;

unstructured objects and structured data about objects from the first and/or second relational databases, the structured data including records associated with the encounter but being completely absent of records associated with the subject; and

unstructured objects and structured data about objects from the first and/or second relational databases, the structured data including records associated with the subject and the encounter.

2. The API of claim 1 , wherein the API is invoked to search, manipulate and/or share data in the first relational database without concern for confidentiality related to revealing personal data associated with the subject or the encounter.

3. The API of claim 1 , wherein the API is invoked to restore data stored in the first relational database into patient specific data when accessed by authorized personnel.

4. The API of claim 1 , wherein the API operates between the first and second relational databases allowing authorized communication therebetween.

5. The API of claim 1 , wherein the API is integrated within an imaging system.

6. The API of claim 1 , wherein the API comprises a user interface allowing access thereto and a directory manager including rules, permissions, methods and logs.

7. The API of claim 1 , wherein data files are stored having an original name associated therewith in a code not accessible by a user of the API and wherein the data files are relabeled based on user preferences leaving the original name intact.

8. The API of claim 1 , wherein the API is invoked by system software of a device, the API is read for data in a target storage location and/or the API is invoked periodically using a scheduler.

9. The API of claim 1 , wherein the API is invoked to automatically create a structured file object by combining structured records stored in tagged files with one or more of the unstructured file or image objects in the first and/or second relational databases.

10. The API of claim 1 , wherein the API is invoked to convert data obtained and stored in a first format to a distinctly different format.

11. The API of claim 10 , wherein data exported via the API is consumable by a third independent and distinct relational database that shares a common ontology regardless of origin of the data.

12. The API of claim 1 , wherein the API is invoked to automatically publish source data to digital imaging and communication (DICOM) conformant files independent of source of metadata associated with the source data or the format source object.

13. The API of claim 1 , wherein the first relational database includes records related to the one or more unstructured objects that have been completely stripped of all protected health information (PHI) associated with the subject and the encounter and wherein the second relational database includes records associated with the subject and the encounter including any relevant PHI.

14. The API of claim 1 , wherein invoking the API causes the API to automatically populate the first relational database and wherein the first relational database includes a coded-link between each object therein and a unique event linked to a subject in second relational database.

15. The API of claim 1 , wherein automatically populating the first relational database comprises:

searching a target data lake for objects that match results of a query initiated from the second relational database;

identifying an object in the target data lake;

automatically populating a storage path identifier for the object into the first relational database; and

returning to the second relational database a key that links a subject record in the second relational database to the object record in the first relational database.

16. The API of claim 15 , wherein populating the first relational database comprises populating the first relational database with additional records descriptive of an object drawn from the data lake, including one or more of a file type, a file size, a file creation date and time stamp.

17. The API of claim 15 , wherein populating the relational database comprises populating the first relational database with additional records descriptive of an object that is drawn from a record, including one or more of an activity type that defines an event creating the object, an anatomy or component of a subject that is the subject of the object, a gender of the subject, an age of the subject at a time of the object curation, a pathological diagnosis or condition of the subject at a time of object creation, a method type that defines creation of the object, a hardware definition that defines equipment used to generate the object, a configuration set that defines operating conditions at use in the creation of the object and a calibration set that provides for quantitative interpretation of the object.

18. The API of claim 1 , wherein the API includes processes and a user interface, where at least one method automatically constructs a database of metadata representative of image objects and the user interface provides a graphical display of contents of the image objects referenced in the database.

19. An imaging system comprising an application programming interface (API) resident on a computer that, upon receiving a message that a data set associated with an encounter experienced by a subject is available, causes a processor to:

read a structured file associated with the data set, the structured file having a set of records assigned to a subset of pre-defined fields and a location of one or more unstructured objects, the pre-defined fields being organized according to an ontology having at least records related to the subject, the encounter and the data set; and

populate at least first and second independent and distinct relational databases using endpoints of the API, the first relational database including records related to the one or more unstructured objects and excluding records associated with the subject and the encounter and the second relational database including records associated with the subject and the encounter,

wherein a schema of the second relational database includes at least a first addressable table that includes protected data associated with the subject and the encounter and at least a second addressable table that excludes protected data associated with the subject and the encounter;

wherein a set of addressable processes of the API are invoked to export one or more of:

unstructured objects and structured data about objects from the first relational database, the structured data being completely absent of records associated with the subject and the encounter;

unstructured objects and structured data about objects from the first and/or second relational databases, the structured data including records associated with the encounter but being completely absent of records associated with the subject; and

unstructured objects and structured data about objects from the first and/or second relational databases, the structured data including records associated with the subject and the encounter.

Assignments (1)

Continuity (2)

References Cited (45)