Healthcare organization record identifier assignment management system

• US 7,318,059 B2
• Filed: 10/24/2005
• Issued: 01/08/2008
• Est. Priority Date: 03/16/2002
• Status: Expired due to Term

• Current Assignee: Cerner Innovation, Inc. (Oracle Corporation)
• Original Assignee: Siemens Medical Solutions Health Services Corporation (Siemens AG)
• Inventors: Thomas, Denise Marie, Grant, John E., Curtis, Gaylene
• Primary Examiner(s): Gafrin; Jeffrey
• Assistant Examiner(s): MAHMOUDI, HASSAN
• Application Number:
  US11/256,865
• Publication Number:
  US 20060036468A1
• Time in Patent Office: 806 Days
• Field of Search: 707/3, 707/4, 707/5
• US Class Current: 1/1
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 40/20 for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation
• CPC Class Codes: Y10S 707/99935 Query augmenting and refining, e.g. inexact access
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

A system (100) for providing multiple facility healthcare corporations the ability to assign and maintain shared medical record numbers (43) across multiple entities. The system establishes a parent/child relationship among the entities to share medical record number ranges, formats, and data. A patient record identifier database (102) contains patient records in a searchable unit record file (50) and an identification number file (3). A search processor (105) locates relevant records and a rules processor (104) applies various tests to the returned data in order to assign a medical record number (43, 13) to a single unique unit reference number (2, 5, 11) to a person without duplication or conflict with identifiers used at other entities (4, 9, 190). The reference numbers and their associated medical records are shared among the various entities. The sharing relationships may be altered by authorized users accessing on line file maintenance (312) and programs (311).

Claims

1. A central record management system for assigning a patient specific record identifier for use by a plurality of healthcare related organizations, said plurality of organizations including individual organizations potentially having an existing record identifier associated with said patient, comprising:

a search processor for determining, for a plurality of organizations, an identifier associated with a particular patient and used by an individual organization of said plurality of organizations;

a rules processor for examining determined identifiers and for assigning a patient specific record identifier for use by said plurality of organizations based on predetermined identifier allocation rules for preventing assignment of the same identifier to different patients; and

a database for storing said assigned patient specific record identifier, wherein if said search processor determines a first identifier is used by a first organization for a second patient different from said particular patient and said first identifier is also used by a second organization of said plurality of organizations for said particular patient, said rules processor assigns a patient specific identifier unused by patients in said plurality of organizations.

2. A system according to claim 1, wherein said unused patient specific identifier is assigned in response to a request from said first organization initiated to support admission of said particular patient at said first organization.

3. A system according to claim 1, wherein said unused patient specific identifier is derived from at least one of, (a) a plurality of predetermined identifiers designated for assignment and (b) an identifier generator for generating identifiers based on a predetermined identifier creation method.

4. A central record management system for assigning a patient specific record identifier for use by a plurality of healthcare related organizations, said plurality of organizations including individual organizations potentially having an existing record identifier associated with said patient, comprising:

a search processor for determining, for a plurality of organizations, an identifier associated with a particular patient and used by an individual organization of said plurality of organizations;

a rules processor for examining determined identifiers and for assigning a patient specific record identifier for use by said plurality of organizations based on predetermined identifier allocation rules for preventing assignment of the same identifier to different patients; and

a database for storing said assigned patient specific record identifier, wherein said search processor determines a first identifier is used by a first organization and a second identifier is used by a second organization of said plurality of organizations for said particular patient, said rules processor assigns said patient specific record identifier based on at least one of, (a) said patient specific identifier is assigned to be one of said first and said second identifiers based on a comparison of said first and said second identifiers and (b) said patient specific identifier is assigned to be one of said first and said second identifiers based on whether said identifier assignment is in response to a request from said first organization or said second organization.

5. A system according to claim 4, wherein if said search processor determines no patient specific identifier, for said particular patient, is used by said plurality of organizations, said rules processor assigns a patient specific identifier derived from at least one of, (a) a plurality of predetermined identifiers designated for assignment and (b) an identifier generator for generating identifiers based on a predetermined identifier creation method.

6. A system according to claim 4, wherein if said search processor determines a single patient specific identifier, for said particular patient, is used by one of said plurality of organizations, said rules processor assignment of said patient specific record identifier comprises adopting said single patient specific identifier for use by said plurality of organizations.

7. A system according to claim 4, wherein said request from said first organization or said second organization is initiated in response to admission of said particular patient at said first organization or said second organization.

8. A system according to claim 4, wherein if said rules processor determines said first and said second identifiers are substantially the same said rules processor assigns a patient specific identifier unused by patients in said plurality of organizations.

9. A central record management system for assigning a patient specific record identifier for use by a plurality of healthcare related organizations, said plurality of organizations including individual organizations potentially having an existing record identifier associated with said patient, comprising:

a search processor for determining, for a plurality of organizations, an identifier associated with a particular patient and used by an individual organization of said plurality of organizations;

a rules processor for examining determined identifiers and for assigning a patient specific record identifier for use by said plurality of organizations in response to a request from a first organization of said plurality of organizations initiated to support admission of said particular patient at said first organization, said patient specific identifier being generated based on predetermined identifier allocation rules for preventing assignment of the same identifier to different patients; and

a database for storing said assigned patient specific record identifier, wherein if said search processor determines a first identifier is used by said first organization and a different second identifier is used by second organization of said plurality of organizations for said particular patient, said rules processor assigns said patients specific record identifier based on at least one of, (a) said patients specific identifier is assigned to be one of said first and said second identifiers based on a comparison of said first and said second identifiers and (b) said patient specific identifier is assigned to be said first identifier based on said first organization being a current admitting organization for said particular patient.

10. A system according to claim 9, wherein if said search processor determines a single patient specific identifier, for said particular patient, is used by said first organization and others of said plurality of organizations do not have an identifier for said particular patient, said rules processor assignment of said patient specific record identifier comprises adopting said single patient specific identifier for use by said plurality of organizations.

11. The system according to claim 9 further comprising a conversion program for interacting with a previous scheme of identifier format and assignment used by at least one of the first and second organizations, the conversion program adopting the scheme of identifier format and assignment whenever the scheme poses no conflict with identifier assignments made by the rules processor.

12. The system according to claim 11, wherein if the conversion program detects a conflicting identifier format adopted under the previous scheme the rules processor creates a new patient specific record identifier.

13. The system according to claim 12, wherein if the conversion program detects some conflicting identifiers adopted under the previous scheme and detects some nonconflicting identifiers adopted under the previous scheme, the conversion program merges the nonconflicting identifiers with the new patient specific record identifiers assigned by the rules processor into a single unit record file.

14. A method of managing demographic records in an organization having a plurality of entities, comprising the steps of:

(a) creating a unit record file;

(b) creating an identification number file;

(c) creating application specific files;

(d) creating a unique person specific record identifier for use by said plurality of entities that resides in the unit record file, the identification number file and each application specific file; and

(e) searching every file for the presence of the person specific record identifier so as to link each file to all other files containing the same unique person specific record identifier.

(f) resolving conflicts in the person specific record identifier protocol by;

(1) assigning to a person with either no identifier or an identifier being used by another person the lowest available person specific identifier that has not already been assigned by any entity in the sharing relationship;

(2) assigning to a person with only one identifier the existing persons specific identifier previously assigned by any entity in the sharing relationeship; and

(3) assigning to a person with a plurality of identifiers the existing person specific identifier assigned by the entity currently providing services to the person, unless none of the identifiers was assigned by the entity currently providing services, in which case the lowest existing person specific identifier will be assigned to the person.

15. The method of claim 14, further comprising the step of creating a person specific record identifier protocol adapted to create a new person specific record identifier whenever the same identifier is used to refer to different people.

16. The method of claim 15, further comprising the steps of:

(a) creating a file sharing relationship between at least two of the entities in the organization; and

(b) sharing a person specific record identifier found in at least one of the files with each of the files accessible to each entity in the file sharing relationship.

17. The method of claim 16, further comprising the steps of:

(a) creating a parent/child relationship between at least two entities in the organization;

(b) permitting all files in the child entity to be accessible to the parent entity; and

(c) permitting at least some files in the parent entity to be accessible to the child entity.