US20240194309A1

US20240194309A1 - Immunization verification system and method

Info

Publication number: US20240194309A1
Application number: US18/534,436
Authority: US
Inventors: Matt Guthrie; Dennis Cronin
Original assignee: Stchealth LLC
Current assignee: Stchealth LLC
Filing date: 2023-12-08
Publication date: 2024-06-13

Abstract

A heath records management system may comprise a software application for operation on a user device including a processor configured for manipulation of health records associated with a user a tangible, non-transitory electronic memory in electronic communication with the processor the tangible, non-transitory memory having instructions stored thereon that, in response to execution by the processor, cause the process to perform operations comprising receiving an authorization request to access the networked database system, transmitting to an electronic immunization registry system of a recording agency, a first Health Level 7 (HL7) formatted request for the recording agency's electronic immunization records of an individual, receiving from the electronic immunization registry system of the recording agency, the first recording agency immunization records of the individual in an HL7 compatible format.

Description

CROSS REFERENCE TO RELATED APPLICATION

This application is a non-provisional of and claims priority to U.S. Provisional Application No. 63/431,626, filed Dec. 9, 2022, which is herein incorporated by this reference in its entirety.

TECHNICAL FIELD

The present disclosure generally relates to database management, and more particularly, to systems that reconcile and integrate information from multiple separated databases, for example government-controlled databases located in different states.

BACKGROUND

Current health records technologies suffer from gaps in the healthcare software space. For example, after an immunization is given, the administering agent (typically a pharmacy, hospital, doctor's office, or other health care facility) is often responsible for submitting records of the immunization to a recording agency—typically a state and/or federal body with statutory authority to maintain these records. Historically it has been sufficient for the administering agent to meet federal and state requirements for reporting simply by indicating the immunization record was submitted to the recording agency. In light of the renewed global focus on pandemic preparation, it is of increasing importance that the administering agent also be able to show that the immunization record was successfully recorded by the recording agency. Furthermore, the time between reporting and actual recording is of increasing importance. Traditional systems tended to take days, but the need for accurate and timely data demands that immunization records should be updated in hours.

SUMMARY

In various embodiments a heath records management system may comprise a software application for operation on a user device including a processor configured for manipulation of health records associated with an individual a tangible, non-transitory electronic memory in electronic communication with the processor the tangible, non-transitory memory having instructions stored thereon that, in response to execution by the processor, cause the process to perform operations comprising receiving an authorization request to access the networked database system, transmitting to an electronic immunization registry system of a recording agency, a first Health Level 7 (HL7) formatted request for the recording agency's electronic immunization records of an individual, receiving from the electronic immunization registry system of the recording agency, the first recording agency immunization records of that individual in an HL7 compatible format, receiving from a computer based system associated with at least one of the lab provider or the healthcare provider, electronic health records associated with that individual, transmitting to the electronic immunization registry system of the recording agency, the electronic health records associated with that individual wherein the electronic health records associated with that individual comprise a new immunization record, transmitting to an electronic immunization registry system of the recording agency, a second HL7 formatted request for the recording agency's electronic immunization records of that individual, receiving from the electronic immunization registry system of the recording agency, a second recording agency immunization records of that individual in an HL7 compatible format, comparing the first recording agency immunization records of that individual and the second recording agency immunization records of that individual, and verifying based on the first recording agency immunization records of that individual and the second recording agency immunization records of that individual acceptance of the new immunization record by the electronic immunization registry system of the recording agency.
In various embodiments, the system may start a first wait timer process and query with the second HL7 formatted request, the electronic immunization registry system of the recording agency in response to the completing of the first wait time process. In various embodiments, the system may start a query loop process in response to determining the new immunization record was not found in the second recording agency immunization records of the individual, wherein the processor periodically queries the electronic immunization registry system of the recording agency. In various embodiments, the system may end the query loop process in response to receiving the new immunization record from the electronic immunization registry system of the recording agency or end the query loop process in response to a loop timer threshold.
The contents of this summary section are provided only as a simplified introduction to the disclosure and are not intended to be used to limit the scope of the appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

With reference to the following description, appended claims, and accompanying drawings:

FIG. 1 is a block diagram illustrating exemplary health records management system components, in accordance with various embodiments;

FIG. 2 is a block diagram illustrating exemplary consumer health record access system architecture, in accordance with various embodiments; and

FIG. 3 illustrates a verification process in an exemplary consumer health record access system in accordance with various embodiments.

DETAILED DESCRIPTION

In response to the recent COVID pandemic and resulting fast-tracked immunizations, there is increased pressure for entities performing immunizations (i.e. the “reporting agency”) to verify that federal and state reporting guidelines are met in an aggressive and timely manner. Existing software based immunization reporting systems struggle to meet this technical challenge. Prior art systems typically include the technical problem of being unable to verify that reporting agency information is in fact recorded accurately at the recording agency tending traditionally to entail a lengthy manually directed verification process. In response to this challenge the present system provides an improvement by not only conveying the immunization record to the appropriate immunization recording agencies (i.e. the “recording agency”) but also, in an automated manner, verifying the immunization has been accepted and recorded by the recording agency. The present system reduces the delay and cost of reconciling immunization records between the immunization provider (i.e. the “reporting agency”) and the recording agency, thus allowing expectations of timely and verified reporting to be met. Instead of record-by-record comparisons of reports from the two agencies, the present system provides, in an automated manner, positive or negative verification that the reported immunization in fact has been both accepted and recorded by the recording agency's system. In this way, a single report can show the necessary reconciliation and outstanding records yet to be recorded. Importantly, the systems and methods described herein accomplish this technical solution without requiring new functionality from the reporting agencies or from the recording agencies and without requiring any other changes in the immunization ecosystem. In various embodiments, the system may automatically return said verification to the reporting agency (within a user definable time horizon i.e., several minutes to several hours).
A health records management system may be any system configured to facilitate storage and/or transmission of health records information, for example information regarding immunizations. With reference now to FIG. 1 , in various exemplary embodiments a health records management system, for example system 115, is configured to provide vaccine administration records functionality, reminders, vaccination reports, vaccine inventory levels, demand forecasts, and the like.
In general, system 115 may comprise any systems, components, and/or software (e.g., system application(s) 145) configured with any suitable methods, algorithms, and/or techniques for health records management. Additionally, system 115 may also suitably interface with any number and/or type of external systems 160, for example client computers, medical provider computers, government computers (e.g., a recording agency) and the like, for example via a common network such as the Internet.
Principles of the present disclosure contemplate improved health records management methods and systems. By providing a centralized repository for health records, system users can achieve faster and simpler access to immunization information, immunization reminders, family member evaluations, and so forth. Moreover, systems and methods configured in accordance with principles of the present disclosure result in improved public health outcomes, for example increased immunization levels.
In various exemplary embodiments, according to principles of the present disclosure, systems and methods are configured to provide conditioned access to public health records, for example immunization records. As opposed to conventional medical records systems that leverage the electronic medical records of a clinical healthcare provider, systems and methods of the present disclosure leverage a central population public health data system (for example, one or more state immunization registries).
In various embodiments, exemplary health records management systems include a user interface (“UI”), software, logic engines, various databases, interfaces to systems and tools, and/or computer networks. While exemplary health records management systems may contemplate upgrades or reconfigurations of existing processes and/or systems, changes to existing databases and system tools are not necessarily required by principles of the present disclosure.
As used herein, an “entity” may include any individual, software program, business, organization, government entity, web site, system, hardware, and/or any other entity. A “user” may include any entity that interacts with a system and/or participates in a process. In various exemplary embodiments, a user is one or more of a consumer, a healthcare provider, or a representative of a state immunization registry.
As illustrated in FIG. 1 , in accordance with various embodiments, a user 105 may perform tasks such as requesting, retrieving, receiving, updating, analyzing and/or modifying data. User 105 may also perform tasks such as initiating, manipulating, interacting with or using a software application, tool, module or hardware, and initiating, receiving or sending a communication. User 105 may interface with Internet server 125 via any communication protocol, user device or method discussed herein, known in the art, or later developed. User 105 may be, for example, a patient, a medical provider, a recording agency records administrator, a health records provider, and/or the like. In various embodiments, a user device may comprise software and/or hardware in communication with the system via a network comprising hardware and/or software configured to allow a transaction account owner, a user, and/or the like, access to the health records system 115. The user device may comprise any suitable device that is configured to allow a user to communicate with a network and the health records system 115. The user device may include, for example, a personal computer, personal digital assistant, cellular phone, tablet, kiosk, and/or the like and may allow a user to transmit biometric information, voice communications, and/or the like
In various embodiments, a health records management system 115 may provide access to a user 105 interfacing with system 115 by way of a client 110. Health records management system 115 may be a partially or fully integrated system comprised of various subsystems, modules and databases. Client 110 comprises any hardware and/or software suitably configured to facilitate entering, accessing, requesting, retrieving, updating, analyzing, and/or modifying data. The data may include health records (e.g., patient information, provider information, medical procedure information, clinical information, diagnostic information, immunization records, prescription information, family information, genetic information, and/or the like), or any other suitable information discussed herein.
Client 110 includes any device (e.g., a computer), which communicates, in any manner discussed herein, with health records management system 115 via any network or protocol discussed herein. Browser applications comprise Internet browsing software installed within a computing unit or system to conduct online communications and transactions. These computing units or systems may take the form of personal computers, mobile phones, personal digital assistants, mobile email devices, laptops, notebooks, hand-held computers, portable computers, tablets, kiosks, and/or the like. Practitioners will appreciate that client 110 may or may not be in direct contact with health records management system 115. For example, client 110 may access the services of health records management system 115 through another server, which may have a direct or indirect connection to Internet server 125. Practitioners will further recognize that client 110 may present interfaces associated with a software application or module that are provided to client 110 via application graphical user interfaces (GUIs) or other interfaces and are not necessarily associated with or dependent upon Internet browsers or internet specific protocols.
User 105 may communicate with health records management system 115 through a firewall 120, for example to help ensure the integrity of health records management system 115 components. Internet server 125 may include any hardware and/or software suitably configured to facilitate communications between the client 110 and one or more health records management system 115 components.
Firewall 120, as used herein, may comprise any hardware and/or software suitably configured to protect health records management system 115 components from users of other networks. Firewall 120 may reside in varying configurations including stateful inspection, proxy based and packet filtering, among others. Firewall 120 may be integrated as software within Internet server 125, or another system 115 component, or may reside within another computing device or may take the form of a standalone hardware component.
Authentication server 130 may include any hardware and/or software suitably configured to receive authentication credentials, encrypt and decrypt credentials, authenticate credentials, and/or grant access rights according to pre-defined privileges associated with the credentials. Authentication server 130 may grant varying degrees of application and/or data level access to users based on information stored within authentication database 135 and user database 140. Application server 142 may include any hardware and/or software suitably configured to serve applications and data to a connected client 110.
In accordance with various embodiments, health records management system 115 is usable to: register and/or pre-register consumers for access to the system; provide consumers (e.g., individuals such as healthcare patients and immunization recipients) and healthcare providers (e.g., doctors, clinics, hospitals, immunization providers, and/or the like) access to health care records; generate health service reminders and/or notifications, for example immunization reminders; deliver data to, retrieve data from, and/or transfer data between one or more recording agencies (such as, for example, States), healthcare providers, and/or consumers; and/or the like. In various embodiments, health records management system 115 utilizes and/or allows communication with a primary database 150, and with various other databases, tools, UIs and systems, for example external systems and databases 160. Such systems include, for example, recording agencies (such as, for example, State immunization registries), healthcare provider systems, third-party health records management systems (for example, the “Health Vault” product offered by Microsoft Corporation), and/or the like.
Health records management system 115 components may be interconnected and communicate with one another to allow for a completely integrated health records management system.
In various embodiments, certain health records management system 115 application(s) 145 are all or a part of software applications configured to enable online functions such as sending and receiving messages, receiving query requests, configuring responses, dynamically configuring user interfaces, requesting data, receiving data, displaying data, executing complex processes, calculations, forecasts, mathematical techniques, workflows and/or algorithms, prompting user 105, verifying user responses, authenticating the user, initiating health records management system 115 processes, initiating portions or all of other software applications, triggering downstream systems and processes, encrypting and decrypting, and/or the like. Additionally, health records management system 115 application(s) 145 may include any hardware and/or software suitably configured to receive requests from client 110, for example via Internet server 125 and application server 142. It will be appreciated that, while application 145 is illustrated as a single application in FIG. 1 , in various embodiments components of health records management system 115 (and/or functionality thereof) may be combined into fewer applications, modules, or components, or, in some embodiments, divided into additional applications, modules, and/or components.
Health records management system 115 application(s) 145 may be further configured to process requests, execute transactions, construct database queries, and/or execute queries against databases within system 115 (e.g., database 150), external data sources and/or temporary databases. In various embodiments, one or more health records management system 115 application(s) 145 may be configured to execute application programming interfaces in order to communicate with a variety of messaging platforms, such as email systems, wireless communications systems, mobile communications systems, multimedia messaging service (“MMS”) systems, short messaging service (“SMS”) systems, and the like.
Health records management system 115 application(s) 145 may be configured to exchange data with other systems, applications, and/or modules, for example, a state immunization registry, and/or the like. In various embodiments, health records management system 115 application(s) 145 may be configured to interact with sub-applications, sub-modules, other systems, or components thereof to perform complex calculations, retrieve additional data, format data into reports, create XML representations of data, construct markup language documents, construct, define or control UIs, and/or the like. Moreover, health records management system 115 application(s) 145 may reside as standalone systems or tools or may be incorporated with the application server 142 or any other health records management system 115 component as program code. As one of ordinary skill in the art will appreciate, health records management system 115 application(s) 145 may be logically or physically divided into various subcomponents, such as a workflow engine configured to evaluate predefined rules and to automate processes.
In addition to the components described above, health records management system 115 may further include one or more of the following: a host server or other computing systems including a processor for processing digital data; a memory coupled to the processor for storing digital data; an input digitizer coupled to the processor for inputting digital data; an application program stored in the memory and accessible by the processor for directing processing of digital data by the processor; a display device coupled to the processor and memory for displaying information derived from digital data processed by the processor; a plurality of databases; a network interface for communicating with external electronic devices; and/or the like.
As will be appreciated by one of ordinary skill in the art, one or more health records management system 115 components may be embodied as a customization of an existing system, an add-on product, upgraded software, a stand-alone system (e.g., kiosk), a distributed system, a method, a data processing system, a device for data processing, and/or a computer program product. Accordingly, individual health records management system 115 components may take the form of an entirely software embodiment, an entirely hardware embodiment, or an embodiment combining aspects of both software and hardware. Furthermore, individual health records management system 115 components may take the form of a computer program product on a computer-readable storage medium having computer-readable program code means embodied in the storage medium. Any suitable computer-readable storage medium may be utilized, including magnetic storage devices (e.g., hard disks), optical storage devices, (e.g., DVD-ROM, CD-ROM, etc.), electronic storage devices (e.g., flash memory), and/or the like.
A computer-readable storage medium can comprise non-volatile memory (e.g., read only memory (ROM)) and/or volatile memory (e.g., random access memory (RAM)). The non-volatile memory can be removable and/or non-removable non-volatile memory. Meanwhile, RAM can comprise dynamic RAM (DRAM), static RAM (SRAM), or some other type of RAM. Further, ROM can include mask-programmed ROM, programmable ROM (PROM), one-time programmable ROM (OTP), erasable programmable read-only memory (EPROM), electrically erasable programmable ROM (EEPROM) (e.g., electrically alterable ROM (EAROM) and/or flash memory), or some other type of ROM. A computer-readable storage medium can comprise non-transitory memory and/or transitory memory. All or a portion of a computer-readable storage medium can be referred to as memory storage module(s) and/or memory storage device(s). A computer-readable storage medium can have a number of form factors when used in systems and methods for immunization verification. For example, the computer-readable storage medium can comprise a magnetic disk hard drive, a solid state hard drive, a removable USB storage drive, a RAM chip, etc.
A computer-readable storage medium can be encoded with a wide variety of computer code configured to operate systems and methods for immunization verification. For example, portions of a computer-readable storage medium can be encoded with a boot code sequence suitable for restoring systems and methods for immunization verification to a functional state after a system reset. As another example, portions of systems and methods for immunization verification can comprise microcode such as a Basic Input-Output System (BIOS) operable with elements of systems and methods for immunization verification. Further, portions of the memory a computer-readable storage medium can comprise an operating system (e.g., a software program that manages the hardware and software resources of a computer and/or a computer network). The BIOS can be configured to initialize and test components of systems and methods for immunization verification and load the operating system. Meanwhile, the operating system can perform basic tasks such as, for example, controlling and allocating memory, prioritizing the processing of instructions, controlling input and output devices, facilitating networking, and/or managing files. Exemplary operating systems can comprise software within the Windows®, UNIX®, Linux®, Solaris®, MacOS®, iOS®, Android®, Windows Mobile OS®, Windows CE®, Palm OS®, Symbian OS®, Blackberry OS®, J2ME®, and other series of operating systems.
As used herein, “computer-readable storage medium” does not include transitory phenomena such as propagating electromagnetic signals. The term “non-transitory” is to be understood to remove only propagating transitory signals per se from the claim scope and does not relinquish rights to all standard computer-readable media that are not only propagating transitory signals per se. Stated another way, the meaning of the term “non-transitory computer-readable medium” and “non-transitory computer-readable storage medium” should be construed to exclude only those types of transitory computer-readable media which were found in In Re Nuijten to fall outside the scope of patentable subject matter under 35 U.S.C. § 101.
Client 110 may also include an operating system (e.g., Windows®, UNIX®, Linux®, Solaris®, MacOS®, iOS®, Android®, Windows Mobile OS®, Windows CE®, Palm OS®, Symbian OS®, Blackberry OS®, J2ME®, etc.) as well as various conventional support software and drivers typically associated with mobile devices and/or computers. Client 110 may be in any environment with access to any network, including both wireless and wired network connections. In various embodiments, access is through a network or the Internet through a commercially available web-browser software package. Client 110 and health records management system 115 components may be independently, separately or collectively suitably coupled to the network via data links which include, for example, a connection to an Internet Service Provider (ISP) over the local loop as is typically used in connection with standard wireless communications networks and/or methods, such as modem communication, cable modem, satellite networks, ISDN, digital subscriber line (DSL), and/or the like. In various embodiments, any portion of client 110 may be partially or fully connected to a network using a wired (“hard wire”) connection. As those skilled in the art will appreciate, client 110 and/or any of the system components may include wired and/or wireless portions.
In various embodiments, components, modules, and/or engines of health records management system 115 may be implemented as micro-applications or micro-apps. Micro-apps are typically deployed in the context of a mobile operating system, including for example, a Palm mobile operating system, a Windows mobile operating system, an Android operating system, Apple iOS, a Blackberry operating system, and the like. The micro-app may be configured to leverage the resources of the larger operating system and associated hardware via a set of predetermined rules which govern the operations of various operating systems and hardware resources. For example, where a micro-app desires to communicate with a device or network other than the mobile device or mobile operating system, the micro-app may leverage the communication protocol of the operating system and associated device hardware under the predetermined rules of the mobile operating system. Moreover, where the micro-app desires an input from a user, the micro-app may be configured to request a response from the operating system which monitors various hardware components and then communicates a detected input from the hardware to the micro-app.
Internet server 125 may be configured to transmit data to client 110, for example within markup language documents. “Data” may include encompassing information such as commands, messages, transaction requests, queries, files, data for storage, and/or the like in digital or any other form. Internet server 125 may operate as a single entity in a single geographic location or as separate computing components located together or in separate geographic locations. Further, Internet server 125 may provide a suitable web site or other Internet-based graphical user interface, which is accessible by users (such as user 105). In various embodiments, Microsoft Internet Information Server (IIS), Microsoft Transaction Server (MTS), and Microsoft SQL Server, are used in conjunction with a Microsoft operating system, Microsoft NT web server software, a Microsoft SQL Server database system, and a Microsoft Commerce Server. In various embodiments, the well-known “LAMP” stack (Linux, Apache, MySQL, and PUP/Perl/Python) are used to enable health records management system 115. Additionally, components such as Access or Microsoft SQL Server, Oracle, Sybase, InterBase, etc., may be used to provide an Active Data Object (ADO) compliant database management system. In various exemplary embodiments, components of health records management system 115 may comprise and/or utilize a HIPAA-compliant cloud computing resource, for example the Elastic Compute Cloud service offered by Amazon.com, and/or offerings from Rackspace.com, VMware, Windows Azure, and/or the like.
Like Internet server 125, application server 142 may communicate with any number of other servers, databases and/or components through any means known in the art. Further, application server 142 may serve as a conduit between client 110 and the various systems and components of health records management system 115. Internet server 125 may interface with application server 142 through any means known in the art including a LAN/WAN, for example. Application server 142 may further invoke software, such as system application(s) 145, automatically or in response to user 105 requests.
Any of the communications, inputs, storage, databases or displays discussed herein may be facilitated through a web site having web pages. The term “web page” as it is used herein is not meant to limit the type of documents and applications that may be used to interact with the user. For example, a typical web site may include, in addition to standard HTML documents, various forms, Java applets, JavaScript, active server pages (ASP), common gateway interface scripts (CGI), Flash files or modules, FLEX, ActionScript, extensible markup language (XML), dynamic HTML, cascading style sheets (CSS), helper applications, plug-ins, and/or the like.
Continuing to reference FIG. 1 , illustrated are databases that are included in various embodiments. An exemplary list of various databases used herein includes: an authentication database 135, a user database 140, primary database 150 and/or other databases that aid in the functioning of the system. As practitioners will appreciate, while depicted as separate and/or independent entities for the purposes of illustration, databases residing within health records management system 115 may represent multiple hardware, software, database, data structure and networking components. Furthermore, embodiments are not limited to the databases described herein, nor do embodiments necessarily utilize each of the disclosed databases.
Authentication database 135 may store information used in an authentication process, for example user identifiers, passwords, access privileges, user preferences, user statistics, and the like. User database 140 maintains user information and credentials for health records management system 115 users (e.g., user 105).
In various embodiments, primary database 150 is a data repository that may be configured to store a wide variety of comprehensive data for health records management system 115. While depicted as a single logical entity in FIG. 1 , those of skill in the art will appreciate that primary database 150 may, in various embodiments, consist of multiple physical and/or logical data sources. In various embodiments, primary database 150 stores one or more of consumer name, date of birth, street address, phone number, email address, password, security question and answer, sex, consumer relationship information (e.g., spouse, parent, child, guardian, dependent, etc.), immunization type and vaccine family information, immunization date information, administering provider, risk factors, age appropriate schedule of immunizations due or past due or next due, vaccine status (public vs. private), narrative content of an informational nature, and/or the like.
With continued reference to FIG. 1 , in various embodiments, user 105 logs onto an application (e.g., a module) and Internet server 125 may invoke an application server 142. Application server 142 invokes logic in health records management system 115 modules by passing parameters relating to user's 105 requests for data. Health records management system 115 manages requests for data from health records management system 115 modules and/or communicates with internal and/or external components. Transmissions between user 105 and Internet server 125 may pass through a firewall 120 to help ensure the integrity of health records management system 115 components. Practitioners will appreciate that exemplary embodiments may incorporate any number of security schemes or none at all. In various embodiments, Internet server 125 receives requests from client 110 and interacts with various other health records management system 115 components to perform tasks related to requests from client 110.
Internet server 125 may invoke an authentication server 130 to verify the identity of user 105 and assign roles, access rights and/or permissions to user 105. For example, a user 105 may be a consumer, a health records provider, a state administrator, and so forth, and the rights, roles, permissions, and access thereof may be customized and/or limited, as desired. In order to control access to the application server 142 or other components of health records management system 115, Internet server 125 may invoke an authentication server 130 in response to user 105 submissions of authentication credentials received at Internet server 125. In response to a request to access health records management system 115 being received from Internet server 125, Internet server 125 determines if authentication is required and transmits a prompt to client 110. User 105 enters authentication data at client 110, which transmits the authentication data to Internet server 125. Internet server 125 passes the authentication data to authentication server 130 which queries the user database 140 for corresponding credentials. In response to user 105 being authenticated, user 105 may access various applications and their corresponding data sources.
With reference now to FIG. 2 , in various embodiments, a health records management system 115, may be configured as software bus (consumer health record access system 215) which provides comprehensive access to immunization records, for example by and among recording agencies (i.e., state, national, and/or international government sanctioned databases), healthcare providers, and consumers. As opposed to prior systems wherein consumers were required to obtain immunization records from healthcare providers and/or directly from the recording agency, consumer health record access system 215 allows consumers to access immunization records from and/or deliver immunization records to one or more state immunization registries. Additionally, many states previously required that a consumer create a read-only account with a state immunization registry before viewing immunization records; in contrast, via use of consumer health record access system 215, consumers can both retrieve immunization records from a state as well as provide immunization records to a state (for example, a consumer can provide immunization records from State A to State B after the consumer moves from State A to State B).
System 115 may be computer based, and may comprise a processor, a tangible non-transitory computer-readable memory, and/or a network interface, along with other suitable system software and hardware components. A processor can comprise any type of computational circuit. For example, a processor can comprise a microprocessor, a microcontroller, a controller, a complex instruction set computing (CISC) microprocessor, a reduced instruction set computing (RISC) microprocessor, a very long instruction word (VLIW) microprocessor, a graphics processor, a digital signal processor, application specific integrated circuits (ASICs), etc. A processor can be configured to implement (e.g., run) computer instructions (e.g., program instructions) stored on memory devices in system. At least a portion of the program instructions, stored on these devices, can be suitable for carrying out at least part of an immunization verification system and method. Architecture and/or design of a processor can be compliant with any of a variety of commercially distributed architecture families. For example, a processor can have a 32-bit (x86) architecture and/or a 64-bit (x86-64, IA64, and AMD64) architecture. A processor can be configured to perform parallel computing in combination with other elements of a system or method for immunization verification (e.g., in combination with additional processors). Parallel computing can be seen as a technique where multiple elements of a system are used to perform calculations simultaneously. In many embodiments, parallel computing can involve the process of breaking down larger problems into smaller, independent, and/or similar parts that can be executed simultaneously by multiple processors communicating via shared memory. In this way, complex and/or repetitive tasks (e.g., training a predictive algorithm) can be performed faster and with less processing power than without parallel computing.
Instructions stored on the tangible non-transitory memory may allow system 115 to perform various functions, as described herein. In various embodiments, the application server 115 and/or consumer heath record access system service (i.e., service 215) may be configured as a central network element or hub to access various systems, engines, and components of system 115.
A network interface can be configured to connect a system or method for immunization verification to a computer network by wired communication (e.g., a wired network adapter) and/or wireless communication (e.g., a wireless network adapter). Accordingly, a system or method for immunization verification can comprise software and/or hardware components configured to implement the wired and/or wireless communication. Further, the wired and/or wireless communication can be implemented using any one or any combination of wired and/or wireless communication network topologies (e.g., ring, line, tree, bus, mesh, star, daisy chain, hybrid, etc.) and/or protocols (e.g., personal area network (PAN) protocol(s), local area network (LAN) protocol(s), wide area network (WAN) protocol(s), cellular network protocol(s), powerline network protocol(s), etc.). Exemplary network protocol(s) can comprise Bluetooth, Zigbee, Wireless Universal Serial Bus (USB), Z-Wave, Institute of Electrical and Electronic Engineers (IEEE) 802.3 (also known as Ethernet), IEEE 802.11 (also known as WiFi), Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Evolution-Data Optimized (EV-DO), Enhanced Data Rates for GSM Evolution (EDGE), Universal Mobile Telecommunications System (UMTS), Digital Enhanced Cordless Telecommunications (DECT), Digital AMPS (IS-136/Time Division Multiple Access (TDMA)), Integrated Digital Enhanced Network (iDEN), Evolved High-Speed Packet Access (HSPA+), Long-Term Evolution (LTE), WiMAX, etc. The specific communication software and/or hardware implemented can depend on the network topologies and/or protocols implemented, and vice versa. In many embodiments, exemplary communication hardware can comprise wired communication hardware including, for example, one or more data buses, such as, for example, universal serial bus(es), one or more networking cables, such as, for example, coaxial cable(s), optical fiber cable(s), and/or twisted pair cable(s), any other suitable data cable, etc. Further exemplary communication hardware can comprise wireless communication hardware including, for example, one or more radio transceivers, one or more infrared transceivers, etc. Additional exemplary communication hardware can comprise one or more networking components (e.g., modulator-demodulator components, gateway components, etc.). A network interface can be integrated into one or more chassis, circuit boards, and/or buses or be removable (e.g., via a PCI slot on a motherboard). For example, a network interface can be implemented via one or more dedicated communication chips configured to receive various protocols of wired and/or wireless communications.
In various exemplary embodiments, consumer health record access system 215 comprises consumer system 245, provider system 246, recording agency system 247, lab system 248, passport system 248, external data handler 244, consumer health record access database 250, and verification system 252. Consumer health record access system 215 may interface with and/or be capable of communication with one or more external data sources or databases such as, for example, recording agency immunization databases 260 (e.g. State A, State B, State C, . . . State N), lab provider systems 262 (e.g., System 1, System 2, System 3, . . . System N), healthcare provider systems 265 (e.g. System 1, System 2, System 3 . . . System N), consumers/users 205, and/or the like. Consumer health record access system 215 may comprise various interactive web pages, software modules, and/or the like.
Consumer system 245 is configured for use by consumers. In various exemplary embodiments, consumer system 245 is configured to support registering consumers for an account, pending authentication/approval by a participating healthcare provider. Consumer system 245 provides a consumer with timely and relevant public and personal health information including but not limited to immunization-related information. Consumer system 245 also provides consumers with a mechanism to “cohort” (group together) family members under a single consumer account for the purposes of conveniently obtaining copies of their immunization records, for example once each family member is authenticated/approved by a participating healthcare provider.
In certain exemplary embodiments, consumer system 245 provides a consumer with an overview of all recorded immunizations for each approved family member. The source for the recorded immunization data may be any suitable source, but in various embodiments, the data source is the participating state(s) immunization information system or “registry”.
Consumer system 245 is configured to provide a consumer with an immunization forecast (a schedule of recommended immunizations that are coming due, now due, or past due). The forecast may be generated based on any suitable factors. In certain embodiments, the forecast is determined in accordance with national recommendations from the U.S. Centers for Disease Control and Prevention, and/or from state-specific immunization schedule requirements.
Consumer system 245 is configured to provide a consumer with one or more electronic copies (for example, in PDF format) of an immunization record (for example, an immunization registry-based record) for each authenticated/approved family member. The records are formatted to conform in content and appearance, according to state-specific requirements.
Consumer system 245 provides a consumer with a feedback mechanism (for example, via a web forum), allowing the collection of user-experience, testimonials, and suggestions, and comprising a vehicle for the establishment of a community-of-users. Additionally, consumer system 245 provides a consumer with an automated reminder function that alerts the consumer (via various modalities) to immunizations that are coming due, now due, or past due for any authenticated/approved family member.
Yet further, consumer system 245 provides a consumer with a mechanism to share, at the consumer's discretion, copies of any of his or her immunization records with third parties (e.g., healthcare providers, a personal health record system, and/or the like) that can receive data formatted according to the federal BlueButton+ standards (a body of standards promulgated and maintained by the U.S. Department of Health and Human Services).
Consumer system 245 provides a consumer with the ability to report to various authorities any perceived discrepancy between their record content (for example, immunization record content) and their personal knowledge (or other source documentation) of their complete immunization history; this allows other authorized entities (e.g., participating healthcare provider) to investigate and resolve discrepancies. Consumer system 245 also provides consumers with non-immunization-related content and functionality, for example personal/household risk assessments, electronic connections with other public health program agencies, preventive health services information, and opportunities to volunteer for participation in state-specific public health oriented surveys, studies, and trials. Consumer system 245 may also provide program, provider, or services locator functionality, or interface with downloadable application(s) for use with smartphone devices and tablet computers.
Consumer system 245 provides a consumer with age-appropriate anticipatory guidance materials for childhood-related health risks, with a look-up feature for participating healthcare providers, and with the ability to obtain electronic copies of immunization records from any state that participates with consumer health record access system 215 (and for which the consumer and their family member(s) have been authenticated and approved in the respective states).
With continued reference to FIG. 2 , provider system 246 is configured for use by healthcare providers. In various exemplary embodiments, provider system 246 allows providers to register and authenticate/approve consumers who request an account, including family members for which he or she requests records access.
Provider system 246 allows providers to look-up consumers who have registered (pending authentication/approval) and to authenticate and approve or reject consumer requests for an account. Moreover, provider system 246 provides providers with relevant public health and personal health information applicable to immunizations as well as other topics.
In certain exemplary embodiments, provider system 246 provides providers with peer-reviewed tools, guidance documents, and patient educational materials pertinent to immunizations, captures demographic and practice-specific information specific to participating providers, and allows provider look-up of view-only records within the state-specific Immunization Information System to which they have been granted approved access.
Provider system 246 may be configured to allow providers to deactivate (suspend) records access permission for any approved consumer or family member. Provider system 246 provides providers with metrics regarding the nature and frequency of consumer health record access system 215 usage by consumers for which the provider has authenticated/approved access.
In various exemplary embodiments, provider system 246 provides providers a user feedback mechanism (for example a web forum, chat room, and/or the like) to allow sharing of comments, suggestions, testimonials, etc., and to create a community of users. Additionally, provider system 246 provides providers a mechanism by which consumers can submit reports of record discrepancies, for example via transmissions using the federal BlueButton+ data exchange standards. Moreover, provider system 246 allows providers to receive the results of consumer risk assessments and other consumer-initiated health information from consumers that voluntarily seek to provide such information to their healthcare provider.
Provider system 246 can provide providers a mechanism to view alerts and other information posted by authorities at the respective state immunization program or registry. Provider system 246 may be configured with a remote lookup capability wherein a provider may view, in read only mode, immunization records for any resident of a state, even if such resident is not a patient of the provider.
With continued reference to FIG. 2 , recording agency system 247 is configured for use by recording agency representatives (e.g., state representatives). For example, recording agency system 247 allows recording agency administrative representatives to create new provider accounts, allows state administrative representatives to deactivate (suspend) previously created provider accounts, and allows recording agency administrative representatives to deactivate (suspend) the accounts of any previously authenticate/approved consumer or family member.
In various exemplary embodiments, recording agency system 247 allows recording agency administrative representatives to create and post informational content (e.g., alerts, guidance, public health information, etc.) to a recording agency specific consumer web page or provider web page. Additionally, recording agency system 247 allows recording agency administrative representatives to view various metrics summarizing system performance and/or pertaining to system usage by consumer and provider account-holders.
In some exemplary embodiments, recording agency system 247 allows recording agency administrative representatives to communicate via e-mail with consumer and provider account-holders, to manage various configurable settings governing recording agency specific application behavior and functionality, and to receive transmissions from account holders sent via BlueButton+ standards. Recording agency system 247 may be configured with analytics capabilities to allow recording agency representatives to visualize trending, provider referral details, and otherwise analyze system use by consumers in their jurisdiction. Recording agency system 247 may also comprise and/or be configured with forecasting tools, for example in order to evaluate potential future immunization needs or other modeled public health requirements or outcomes.
With continued reference to FIG. 2 , lab system 248 is configured for use by lab providers. In various exemplary embodiments, lab system 248 allows lab providers to register and authenticate/approve consumers who request an account, including healthcare providers and/or family members for which he or she requests records access.
Lab system 248 allows providers to look-up consumers who have registered (pending authentication/approval) and to authenticate and approve or reject consumer requests for an account. Moreover, lab system 248 provides providers with relevant public health and personal health information applicable to lab work and immunizations as well as other topics.
In certain exemplary embodiments, lab system 248 provides lab providers with peer-reviewed tools, guidance documents, and patient educational materials pertinent to lab work, captures demographic and practice-specific information specific to participating providers, and allows provider look-up of view-only records within the state-specific healthcare database systems (e.g., healthcare information exchanges) which they have been granted approved access.
Lab system 248 may be configured to allow providers to deactivate (suspend) records access permission for any approved consumer, healthcare provider, or family member. Lab system 248 provides providers with metrics regarding the nature and frequency of consumer health record access system 215 usage by consumers for which the provider has authenticated/approved access.
In various exemplary embodiments, lab system 248 provides providers a user feedback mechanism (for example a web forum, chat room, and/or the like) to allow sharing of comments, suggestions, testimonials, etc., and to create a community of users. Additionally, provider system 246 provides providers a mechanism by which consumers can submit reports of record discrepancies, for example via transmissions using the federal BlueButton+ data exchange standards. Moreover, lab system 248 may enable providers to receive the results of consumer risk assessments and other consumer-initiated health information from consumers that voluntarily seek to provide such information to their healthcare provider.
Lab system 248 can provide providers a mechanism to view alerts and other information posted by authorities at the respective state immunization program or registry. Lab system 248 may be configured with a remote lookup capability wherein a provider may view, in read only mode, immunization records for any resident of a state, even if such resident is not a patient of the provider.
Consumer health record access database 250 stores information utilized by consumer health record access system 215, for example information similar to information stored in primary database 150.
In various exemplary embodiments, consumer health record access system 215 is configured to provide bi-directional Health Level 7 (HL7) messaging capability to state immunization registries and health care providers. For example, the system may communicate using HL7 Update (VXU) and Query (QBP) messages.
In various embodiments, verification system 252 is configured to verify information stored in consumer health records access system 215. For example, verification system 252 may confirm transfers of records between external data sources (e.g., recording agency immunization databases 260, lab provider systems 262, and healthcare provider systems 265) and the consumer health record access database 250. Verification system may be configured to propagate changes in records and ensure that the interconnected internal and external databases maintain parity of records. The verification system 252 may be configured to compare recording agency records across time. For example, where the recording agency is a State, the verification system 252 may be confirmed to compare State A immunization records for a user taken at a first time (i.e., a first recording agency immunization record) with State A immunization records of the user taken at a second time (i.e., second recording agency immunization record) and determine whether there is a change. For example, the verification system 252 may detect a change showing a new immunization record. The verification system 252 may be configured to compare recording agency records across recording agency's (e.g., between a first State and a second State). For example, the verification system 252 may be confirmed to compare State A immunization records for a user taken at a first time (i.e., a first state T1 immunization records) with State B immunization records of the user taken at the first time (i.e., a second state T1 immunization record) and determine whether there is a change. For example, the system may detect a record for the user is present in State B which is not present in State A. It will be appreciated that the verification system 252 may be configured to determine changes across both recording agency and time.
Where a change is detected based on the comparison of the records, the verification system 252 may ensure the change is propagated between the databases. For example, the verification system 252 may transmit the changes and repeatedly query the associated databases to ensure the change is accepted. In this regard, the system may ensure greater data quality and accuracy by providing record verification and confirmation without necessitating design changes on the part of the external data sources (e.g., recording agency immunization databases 260, lab provider systems 262, and healthcare provider systems 265). Importantly, the system provides a translation function enabling interoperation between external data sources which may tend to have incompatible communications protocols.
In various exemplary embodiments, consumer health record access system 215 is configured to provide recording agency-specific or state-required immunization reports or certification forms. Such reports may take the form of official state forms. Stated another way, consumers can access immunization documentation in both informal (i.e., report) form, as well as in formal (i.e., official state documentation) form. In this manner, states can simplify access to and distribution of official state immunization information and forms to consumers.
In various exemplary embodiments, when a consumer moves from State A to State B, the consumer will retain access in consumer health record access system 215 to records from State A, even after being authenticated into new State B. In this manner, centralized access to immunization records is facilitated. Via consumer health record access system 215, a consumer may also share records among states; i.e., a consumer may provide State B immunization information to State A to update the records of State A. Yet further, via consumer health record access system 215, a consumer may instruct that immunization records be provided, in a standardized format and/or protocol such as BlueButton+, to any external record acceptor (for example, healthcare providers, Microsoft Health Vault, and/or the like).
In various exemplary embodiments, consumer health record access system 215 checks immunization records in consumer health record access database 250 on a regular basis (for example, daily, weekly, bi-weekly, monthly, and so forth). Consumer health record access system 215 may be configured to send automated reminders to consumers and/or health care providers regarding upcoming scheduled immunizations, past due immunizations, supplementary recommended immunizations due to public health alerts, and/or the like.
In certain exemplary embodiments, consumer health record access system 215 provides “cohorting” capabilities to a consumer. In these embodiments, a particular consumer (e.g., a parent or guardian) may view and/or access immunization information for other consumers (e.g., a child or ward). In this manner, household immunization information may be centralized, facilitating improved immunization outcomes. For example, an adoptive parent may quickly determine that a particular child lacks a certain immunization previously received by other children in the same household; the parent can then schedule the suggested immunization.
In various exemplary embodiments, consumer health record access system 215 is usable to provide actionable information directly to a consumer based on at least one of the consumer's immunization history, age, gender, or risk. Consumer health record access system 215 supports interjurisdictional information retrieval, allowing a consumer to access his or her immunization records, either alone or in connection with the records of one of more family members, from multiple states. Consumer health record access system 215 is configured to provide seamless integration with other medical records systems, for example as found in retail health, clinical or personal health records, health information exchanges, and the like. Consumer health record access system 215 can provide consumer prevention information, screening data components, medical device integration, family pet immunization histories, and so forth.
In various exemplary embodiments, consumer health record access system 215 allows consumers to pre-register for an account, for example by specifying their desired password and e-mail address. Additionally, consumer health record access system 215 provides consumer-managed cohorting of family members. For example, consumer health record access system 215 can send requests for records access to a provider approval queue for any family member for which a consumer may request records access. Yet further, consumer health record access system 215 allows for provider-managed consumer registration/approval; this approach allows providers to optionally register and approve consumers in their healthcare setting.
In certain exemplary embodiments, consumer health record access system 215 is configured to support provider look-up of matching and/or closely matching records. For example, consumer health record access system 215 allows providers to view, within consumer health record access system 215, attributes of matching or closely matching records, for example records located through an HL7 query to a respective state immunization information system.
Consumer health record access system 215 is configured to provide immunization records reports and/or certificates. In one embodiment, consumer health record access system 215 allows consumers one generic and one or more state-specific views of immunization records that can be printed, stored, or pushed to other destinations.
Consumer health record access system 215 provides third-party consumer and provider educational information and tools. For example, consumer health record access system 215 provides ongoing access to archival and new peer-reviewed reference and educational materials targeted at consumers and providers (respectively).
In some exemplary embodiments, consumer health record access system 215 is configured with BlueButton+ capability. In this manner, consumer health record access system 215 may export copies of immunization records in the federal BlueButton+ format, enabling consumers to share their immunization records with providers and/or personal health records (PHR) service providers or software of their choosing.
Consumer health record access system 215 is configured to provide system performance metrics and analytics. This allows authorized administrative users to monitor system performance, attributes of users, system behavior and usage patterns. Additionally, consumer health record access system 215 is configured with a scalable user interface, permitting consumer health record access system 215 to be accessed and/or utilized on different devices (e.g., computer, tablet, smartphone).
Consumer health record access system 215 is interoperable with any HL7-compliant state immunization registry. In this manner, consumer health record access system 215 may be subscribed to by any state immunization registry.
Moreover, consumer health record access system 215 provides anticipatory guidance (preventive health) information for age-appropriate cohorts of children via consumer accounts, provides consumer health/household risk assessment instruments and analyses, and provides a communications exchange with various public health program areas of a topical nature.
In some exemplary embodiments, consumer health record access system 215 provides automated reminders for immunization and additional preventive health care-associated circumstances, provides provider and preventive services access and locational look-up features, and provides consumer alerting of healthcare providers to possible errors in record content.
In various embodiments and with reference to FIG. 3 , a verification process 1000 of the system 115 is illustrated. The system may receive a new record (e.g., a first recording agency immunization records of an individual) from one of the external data sources (e.g., recording agency immunization databases 260, lab provider systems 262, or healthcare provider systems 264) (step 1002). In response to receiving the record, the system may start a first wait timer process and may propagate the new record to the external sources (step 1004). For example, the wait timer may be configured to expire after 24 hours. In response to expiry of the first wait timer, the system may query the databases for the record (step 1006). For example, the system may send a second HL7 formatted request for the record to the electronic information registry system of the recording agency.
The system may receive the second recording agency immunization records of the individual in response to the second HL7 formatted request. The system may compare the first recording agency immunization records of the individual and the second recording agency immunization records of the individual and find corresponding records (e.g., presence of the new immunization record). In response to finding the corresponding record, the system may generate the confidence metric and assign the confidence metric to the new immunization record (step 1008). The system may verify the new immunization record in response to the confidence metric exceeding a threshold value and, in response, report to the reporting agency that the record is verified (step 1010).
In response to determining the new immunization record was not found in the second first recording agency immunization records of the individual, the system may start a query loop process wherein the system periodically queries the external data sources (step 1012). For example, the system may periodically query the electronic immunization registry system of the recording agency. In response to starting the query loop process, the system may start a loop timer and may end the query loop process in response to a loop timer threshold (step 1014). The system may issue a report to the reporting agency in response to exceeding the loop timer threshold. Otherwise, the system may end the query loop process. For example, the system may end the query loop process in response to receiving the new immunization record from the electronic immunization registry system of the recording agency or verifying the new record has propagated across the external databases.
The following description is of various embodiments only, and is not intended to limit the scope, applicability or configuration of the present disclosure in any way. Rather, the following description is intended to provide a convenient illustration for implementing various embodiments including the best mode. As will become apparent, various changes may be made in the function and arrangement of the elements described in these embodiments without departing from the scope of the present disclosure or appended claims.
It should be appreciated that exemplary components and steps may be realized by any number of hardware, software, or other components configured to perform the specified functions. For example, an exemplary embodiment employs various graphical user interfaces, software components, and networking and/or database functionality. In addition, various embodiments may be practiced in any number of medical record management and/or information management contexts, and the embodiments disclosed are merely indicative of exemplary applications. For example, the principles, features and methods discussed may be applied to various industries and are not limited to use in connection with health records and/or immunizations.
The foregoing description of exemplary embodiments herein makes reference to the accompanying drawings and pictures, which show various embodiments by way of illustration. While these various embodiments are described in sufficient detail to enable those skilled in the art to practice the disclosure, it should be understood that other embodiments may be realized and that logical and/or functional changes may be made without departing from the spirit and scope of the disclosure. Thus, the detailed description herein is presented for purposes of illustration only and not of limitation. For example, the steps recited in any of the method or process descriptions may be executed in various orders and are not limited to the order presented. Moreover, certain of the functions or steps may be outsourced to or performed by one or more third parties. Furthermore, any reference to singular includes plural embodiments, and any reference to more than one component may include a singular embodiment.
Systems, methods and computer program products are provided. In the detailed description herein, references to “an exemplary embodiment”, “various embodiments”, “one embodiment”, “an embodiment”, “an example embodiment”, etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described. After reading the description, it will be apparent to one skilled in the relevant art(s) how to implement the disclosure in alternative embodiments.
As used herein, “match” or “associated with” or similar phrases may include an identical match, a partial match, meeting certain criteria, matching a subset of data, a correlation, satisfying certain criteria, a correspondence, an association, an algorithmic relationship and/or the like. Similarly, as used herein, “authenticate” or similar terms may include an exact authentication, a partial authentication, authenticating a subset of data, a correspondence, satisfying certain criteria, an association, an algorithmic relationship and/or the like.
In various embodiments, the methods described herein are implemented using the various particular machines described herein. The methods described herein may be implemented using the below particular machines, and those hereinafter developed, in any suitable combination, as would be appreciated immediately by one skilled in the art. Further, as is unambiguous from this disclosure, the methods described herein may result in various transformations of certain articles.
For the sake of brevity, conventional techniques for data networking, software application development, cloud computing, and/or the like, may not be described in detail herein. Furthermore, the connecting lines shown in various figures contained herein are intended to represent exemplary functional relationships and/or physical or communicative couplings between various elements. It should be noted that many alternative or additional functional relationships or physical or communicative connections may be present in a practical health records management system.
While the present disclosure may be described in terms of a consumer, a healthcare provider, a recording agency, and so forth, one skilled in the art can appreciate that similar features and principles may be applied to other industries and database environments.
While the exemplary embodiments described herein are described in sufficient detail to enable those skilled in the art to practice principles of the present disclosure, it should be understood that other embodiments may be realized and that logical and/or functional changes may be made without departing from the spirit and scope of the present disclosure. Thus, the detailed description herein is presented for purposes of illustration and not of limitation.
While the description references specific technologies, system architectures and data management techniques, practitioners will appreciate that this description is of various embodiments, and that other devices and/or methods may be implemented without departing from the scope of principles of the present disclosure. Similarly, while the description references a user interfacing with the system via a computer user interface, practitioners will appreciate that other interfaces may include mobile devices, kiosks and handheld devices such as mobile phones, smart phones, tablet computing devices, etc.
While the steps outlined herein represent exemplary embodiments of principles of the present disclosure, practitioners will appreciate that there are any number of computing algorithms and user interfaces that may be applied to create similar results. The steps are presented for the sake of explanation only and are not intended to limit the scope of the present disclosure in any way. Benefits, other advantages, and solutions to problems have been described herein with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and any element(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as critical, required, or essential features or elements of any or all of the claims.
It should be understood that the detailed description and specific examples, indicating exemplary embodiments, are given for purposes of illustration only and not as limitations. Many changes and modifications may be made without departing from the spirit thereof, and principles of the present disclosure include all such modifications. Corresponding structures, materials, acts, and equivalents of all elements are intended to include any structure, material, or acts for performing the functions in combination with other elements. Reference to an element in the singular is not intended to mean “one and only one” unless explicitly so stated, but rather “one or more.” Moreover, when a phrase similar to “at least one of A, B, or C” or “at least one of A, B, and C” is used in the claims or the specification, the phrase is intended to mean any of the following: (1) at least one of A; (2) at least one of B; (3) at least one of C; (4) at least one of A and at least one of B; (5) at least one of B and at least one of C; (6) at least one of A and at least one of C; or (7) at least one of A, at least one of B, and at least one of C.
Any databases discussed herein may include relational, hierarchical, graphical, or object-oriented structure and/or any other database configurations. Common database products that may be used to implement the databases include DB2 by IBM (Armonk, NY), various database products available from Oracle Corporation (Redwood Shores, CA), Microsoft Access or Microsoft SQL Server by Microsoft Corporation (Redmond, Washington), MySQL by MySQL AB (Uppsala, Sweden), Ehcache, Couchbase, VoltDB, Versant, Hazelcast, or any other suitable database product, for example a persistent and distributed in-memory database product. Moreover, the databases may be organized in any suitable manner, for example, as data tables or lookup tables. Each record may be a single file, a series of files, a linked series of data fields or any other data structure. Association of certain data may be accomplished through any desired data association technique such as those known or practiced in the art. For example, the association may be accomplished either manually or automatically. Automatic association techniques may include, for example, a database search, a database merge, GREP, AGREP, SQL, using a key field in the tables to speed searches, sequential searches through all the tables and files, sorting records in the file according to a known order to simplify lookup, and/or the like. The association step may be accomplished by a database merge function, for example, using a “key field” in pre-selected databases or data sectors. Various database tuning steps are contemplated to optimize database performance. Examples include distributing data elements to grid memory, optimizing partitioning of memory objects to process, indexing frequently used files and placing on separate file systems to reduce Input/Output (“I/O”) bottlenecks.
One skilled in the art will also appreciate that, for security reasons, any databases, systems, devices, servers or other components of health records management system 115 may consist of any combination thereof at a single location or at multiple locations, wherein each database or system includes any of various suitable security features, such as firewalls, access codes, encryption, decryption, compression, decompression, and/or the like.
The systems and methods may be described herein in terms of functional block components, screen shots, optional selections and various processing steps. It should be appreciated that such functional blocks may be realized by any number of hardware and/or software components configured to perform the specified functions. For example, the system may employ various integrated circuit components, e.g., memory elements, processing elements, logic elements, look-up tables, and the like, which may carry out a variety of functions under the control of one or more microprocessors or other control devices. Similarly, the software elements of the system may be implemented with any programming or scripting language such as C, C++, C #, Java, JavaScript, Flash, ActionScript, FLEX, VBScript, Macromedia Cold Fusion, COBOL, Microsoft Active Server Pages, assembly, PERL, SAS, PUP, awk, Python, Visual Basic, SQL Stored Procedures, PL/SQL, any UNIX shell script, extensible markup language (XML), and/or the like, with the various algorithms being implemented with any combination of data structures, objects, processes, routines or other programming elements. Further, it should be noted that the system may employ any number of conventional techniques for data transmission, signaling, data processing, network control, and the like. Still further, the system may be used to detect or prevent security issues with a client-side scripting language, such as JavaScript, VBScript and/or the like.
Software elements may be loaded onto a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions that execute on the computer or other programmable data processing means for implementing the functions specified in the flowchart block or blocks. These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified herein or in flowchart block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.
Accordingly, functional blocks of the block diagrams and flowchart illustrations support combinations of means for performing the specified functions, combinations of steps for performing the specified functions, and program instruction means for performing the specified functions. It will also be understood that each functional block of the block diagrams and flowchart illustrations, and combinations of functional blocks in the block diagrams and flowchart illustrations, can be implemented by either special purpose hardware-based computer systems which perform the specified functions or steps, or suitable combinations of special purpose hardware and computer instructions. Further, illustrations of the process flows and the descriptions thereof may make reference to user windows, web pages, web sites, web forms, prompts, etc. Practitioners will appreciate that the illustrated steps described herein may comprise any number of configurations including the use of windows, web pages, web forms, popup windows, prompts and/or the like. It should be further appreciated that the multiple steps as illustrated and described may be combined into single web pages and/or windows but have been expanded for the sake of simplicity. In other cases, steps illustrated and described as single process steps may be separated into multiple web pages and/or windows but have been combined for simplicity.

Claims

What is claimed is:

1. A networked database system including a software application for operation on a user device, the system comprising:

a processor configured for manipulation of health records associated with a user;

a tangible, non-transitory electronic memory in electronic communication with the processor,

the tangible, non-transitory memory having instructions stored thereon that, in response to execution by the processor, cause the process to perform operations comprising:

transmitting, by the processor and to an electronic immunization registry system of a recording agency, a request in a first format for the recording agency electronic immunization records of a patient;

receiving, by the processor and from the electronic immunization registry system of the recording agency, a first recording agency immunization record of the patient in the first format;

receiving, by the processor and from a computer based system associated with at least one of a lab provider or a healthcare provider, electronic health records associated with the user;

transmitting, by the processor and to the electronic immunization registry system of the recording agency, the electronic health records associated with the patient wherein the electronic health records associated with the patient comprise a new immunization record;

transmitting, by the processor and to an electronic immunization registry system of the recording agency, a second request in a second format for the recording agency electronic immunization records of the patient;

receiving, by the processor and from the electronic immunization registry system of the recording agency, a second recording agency immunization records of the patient in the second format;

comparing, by the processor, the first recording agency immunization records of the patient and the second recording agency immunization records of the patient; and

verifying, by the processor and based on the first recording agency immunization records of the patient and the second recording agency immunization records of the patient, acceptance of the new immunization record by the electronic immunization registry system of the recording agency.

2. The system of claim 1, wherein the operations further comprise:

starting, by the processor, a first wait timer process; and

querying, by the processor and with the second request, the electronic immunization registry system of the recording agency in response to the completing of the first wait time process.

3. The system of claim 2, wherein the operations further comprise:

starting, by the processor, a query loop process in response to determining the new immunization record was not found in the second recording agency immunization records of the patient, wherein the processor periodically queries the electronic immunization registry system of the recording agency.

4. The system of claim 3, wherein the operations further comprise

ending, by the processor, the query loop process in response to receiving the new immunization record from the electronic immunization registry system of the recording agency; or

ending, by the processor, the query loop process in response to a loop timer threshold.

5. The system of claim 1, wherein the recording agency electronic immunization records of the patient comprise immunization records for a family of the patient.

6. The system of claim 1, wherein the operations further comprise:

transmitting, to the second recording agency in the first format and the second format, the new immunization record for incorporation into a second recording agency immunization record of the patient.

7. The system of claim 1, wherein the first format comprises a Health Level 7 (HL7) compatible format.

8. A method comprising:

transmitting, by a processor and to an electronic immunization registry system of a recording agency, a request in a first format for the recording agency electronic immunization records of a patient;

9. The method of claim 8 further comprising:

starting, by the processor, a first wait timer process; and

querying, by the processor and with the second HL7 formatted request, the electronic immunization registry system of the recording agency in response to the completing of the first wait time process.

10. The method of claim 9, further comprising:

performing, by the processor, a query loop process in response to determining the new immunization record was not found in the second recording agency immunization records of the individual, wherein the processor periodically queries the electronic immunization registry system of the recording agency.

11. The method of claim 10, further comprising

12. The method of claim 8, wherein the recording agency electronic immunization records of the patient comprise immunization records for a family of the patient.

13. The method of claim 8 further comprising:

14. The method of claim 8, wherein the first format comprises a Health Level 7 (HL7) compatible format.

15. An article of manufacture including a non-transitory, tangible computer readable storage medium having instructions stored thereon that, in response to execution by a processor, cause the processor to perform operations comprising:

16. The article of manufacture of claim 15, wherein the operations further comprise:

starting, by the processor, a first wait timer process; and

17. The article of manufacture of claim 16, wherein the operations further comprise:

starting, by the processor, a query loop process in response to determining the new immunization record was not found in the second recording agency immunization records of the individual, wherein the processor periodically queries the electronic immunization registry system of the recording agency.

18. The article of manufacture of claim 17, wherein the operations further comprise

19. The article of manufacture of claim 15, wherein the recording agency electronic immunization records of the patient comprise immunization records for a family of the patient.

20. The article of manufacture of claim 15, wherein the operations further comprise: