[go: up one dir, main page]

WO2025095979A1 - Systèmes de gestion de dossier de vaccination - Google Patents

Systèmes de gestion de dossier de vaccination Download PDF

Info

Publication number
WO2025095979A1
WO2025095979A1 PCT/US2023/078738 US2023078738W WO2025095979A1 WO 2025095979 A1 WO2025095979 A1 WO 2025095979A1 US 2023078738 W US2023078738 W US 2023078738W WO 2025095979 A1 WO2025095979 A1 WO 2025095979A1
Authority
WO
WIPO (PCT)
Prior art keywords
vaccination
user
record
vaccine
data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/US2023/078738
Other languages
English (en)
Inventor
Marc-David JEAN
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vaccination Card System Sycvac And Red Immunization Card Ric Red Card LLC
Original Assignee
Vaccination Card System Sycvac And Red Immunization Card Ric Red Card LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Vaccination Card System Sycvac And Red Immunization Card Ric Red Card LLC filed Critical Vaccination Card System Sycvac And Red Immunization Card Ric Red Card LLC
Priority to PCT/US2023/078738 priority Critical patent/WO2025095979A1/fr
Publication of WO2025095979A1 publication Critical patent/WO2025095979A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
    • G16H10/60—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records
    • G16H10/65—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records stored on portable record carriers, e.g. on smartcards, RFID tags or CD
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/44—Program or device authentication
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • G06F21/6245—Protecting personal data, e.g. for financial or medical purposes
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
    • G16H10/60—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H20/00—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance
    • G16H20/10—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to drugs or medications, e.g. for ensuring correct administration to patients
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
    • G16H40/20—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H80/00—ICT specially adapted for facilitating communication between medical practitioners or patients, e.g. for collaborative diagnosis, therapy or health monitoring
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/70—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer
    • G06F21/82—Protecting input, output or interconnection devices
    • G06F21/84—Protecting input, output or interconnection devices output devices, e.g. displays or monitors

Definitions

  • FIG. 1 illustrates a vaccination record management system, according to an embodiment
  • FIG. 2 illustrates a device schematic for various devices used in a vaccination record management system, according to an embodiment
  • FIG. 3 il lustrates a device schematic for various devices used in a vaccination record management system for managing a vaccination record using a vaccination record application, according to an embodiment:
  • FIG. 4A illustrates a login screen of a vaccination record application, according to an embodiment
  • FIG. 4B illustrates a password reset screen of a vaccination record application, according to an embodiment
  • FIG. 4C illustrates an interface of a vaccination record applicMion for editing a user profile within the application, according to an embodiment
  • FIG. 4D illustrates a feature of a vaccination record application that allows parents and guardians to manage vaccination records for their children, according to an embodiment
  • FIG. 4E presents a vaccination record displayed in a list format within a vaccination record application, according to an embodiment
  • FIG. 4F illustrates a vaccination record presented in a calendar view, according to an embodiment
  • FIG. 4G illustrates an interface of a vaccination record application for enabling school administrators to efficiently access and review registered children's information and vaccination schedules through the application, according to an embodiment
  • FIG. 5 illustrates a red card within a vaccination record application, according to an embodiment
  • FIG. 6A illustrates a vaccination record application featuring an "Add Child” button, according to an embodiment:
  • FIG. 6B illustrates a layout of a vaccination record application, according to an embodiment
  • FIG. 7 illustrates a layout of a vaccination record application, according to an embodiment
  • FIG. 8 illustrates a layout of a vaccination record application, according to an embodiment
  • FIG. 9 is a flow diagram of a method for managing a vaccination record using a vaccination record application.
  • a vaccination record management system as disclosed herein will become better understood through a review of the following detailed description in conjunction with the figures.
  • the detailed description and figures provide merely examples of the various embodiments of the vaccination record management system. Many variations are contemplated for different applications and design considerations; however, for the sake of brevity and clarity, all the contemplated variations may not be individually described in the following detailed description. Those skilled in the art will understand how the disclosed examples may be varied, modified, and altered and not depart in substance from the scope of the examples described herein.
  • the existing vaccination record management methods face several challenges. Firstly, the reliance on physical cards poses a risk of loss or damage, potentially resulting in the loss of critical vaccination data. Secondly, manual data entry is time-consuming and prone to errors, leading to inaccurate records. Additionally, the lack of user-centric customization and personalization options in current systems limits user engagement and adoption. Lastly, the lack of interoperability between different systems and institutions hinders the efficient sharing of vaccination records, especially in cases of international travel or cross-border healthcare.
  • Implementations of the vaccination record management system aim to resolve many of the aforementioned challenges.
  • the system simplifies the process of capturing vaccination records, reducing the risk of loss or damage associated with physical cards.
  • the customization features including personalized dashboards and language preferences, address the problem of limited user engagement by tailoring the experience to individual preferences.
  • the system's interoperability capabilities facilitate data sharing between healthcare providers and institutions, thereby enhancing the accessibility and completeness of vaccination records.
  • the disclosed embodiment(s) of the vaccination record management system address the above-described issues.
  • the digital interface and recognition system may streamline record capturing, reducing the likelihood of data loss or errors.
  • Customization options cater to individual preferences and enhance user engagement.
  • the system's interoperability features enable efficient data sharing, addressing the challenges associated with fragmented healthcare data systems.
  • the disclosed embodiments may therefore provide a novel vaccination record management by offering a more user-centric, secure, and interconnected solution to the existing challenges in the field.
  • FIG. 1 illustrates a vaccination record management system 100, according to an embodiment.
  • the vaccination record management system 100 includes internal and external data resources for streamlining record capturing and reducing the likelihood of data loss or errors.
  • the vaccination record management system 100 may result in reduced memory allocation at client devices and may conserve memory resources for application servers.
  • the vaccination record management system 100 may include a cloud-based data management system 102 and a user device 104.
  • the cloud-based date management system 102 may Include an application server 106, a database 108, and a data server no.
  • the user device 104 may include one or more devices associated with user profiles of the vaccination record management system 100, such as a smartphone 112 and/or a personal computer 114.
  • the vaccination record management system 100 may include external resources such as an external application server 116 and/or an external database 118.
  • the various elements of the vaccination record management system 100 may communicate via various communication links 120.
  • An external resource may generally be considered a data resource owned and/or operated by an entity other than an entity that utilizes the cloud-based data management system 102 and/or the user device 104.
  • the vaccination record management system 100 may be web-based.
  • the user device 104 may access the cloud-based data management system 102 via an online portal set up and/or managed by the application server 106.
  • the vaccination record management system 100 may be implemented using a public internet
  • the vaccination record management system 100 may be implemented using a private intranet.
  • Elements of the vaccination record management system 100. such as the database 108 and/or the data server 110, may be physically housed at a location remote from an entity that owns and/or operates the vaccination record management system 100. tor example, various elements of the vaccination record management system 100 may be physically housed at a public sendee provider such as a web services provider.
  • Elements of the vaccination record management system 100 may be physically housed at a private location, such as at a location occupied by the entity that owns and/or operates the vaccination record management system 100.
  • the communication links 120 may be direct or indirect
  • a direct link may include a link between two devices where information is communicated from one device to the other without passing through an intermediary.
  • the direct link may include a BluetoothTM connection, a Zigbee* connection, a Wifi DirectTM connection, a near-field communications (NFC) connection, an infrared connection, a wired universal serial bus (USB) connection, an ethernet cable connection, a fiber-optic connection, a firewire connection, a microwire connection, and so forth.
  • the direct link may include a cable on a bus network. “Direct,” when used regarding the communication links 120, may refer to any of the aforementioned direct communication links.
  • An indirect link may include a link between two or more devices where data may pass through an intermediary, such as a router, before being received by an intended recipient of the data.
  • the indirect link may include a wireless fidelity (WiFi) connection where data is passed through a WiFi router, a cellular network connection where data is passed through a cellular network router, a wired network connection where devices are interconnected through hubs and/or routers, and so forth.
  • WiFi wireless fidelity
  • the cellular network connection may be implemented according to one or more cellular network standards, including the global system for mobile communications (GSM) standard, a code division multiple access (CDMA) standard such as the universal mobile telecommunications standard, an orthogonal frequency division multiple access (OFDMA) standard such as the long term evolution (LTE) standard, and so forth.
  • GSM global system for mobile communications
  • CDMA code division multiple access
  • OFDMA orthogonal frequency division multiple access
  • LTE long term evolution
  • FIG. 2 illustrates a device schematic 200 for various devices used in the vaccination record management system 100, according to an embodiment.
  • a server device 200a may moderate data communicated to a client device 200b based on data permissions to mlmimize memory resource allocation at the client device 200b.
  • the server device 200a may include a communication device 202, a memory device 204, and a processing device 206.
  • the processing device 206 may include a data processing module 206a and a data permissions module 206b, where module refers to specific programming that governs how data is handled by the processing device 206.
  • the client device 200b may include a communication device 208, a memory device 210, a processing device 212, and a user interface 214.
  • Various hardware elements within the server device 200a and/or the client device 200b may be interconnected via a system bus 216.
  • the system bus 216 may be and/or include a control bus, a data bus, and address bus, and so forth.
  • the communication device 202 of the server device 200a may communicate with the communication device 208 of the client device 200b.
  • the data processing module 206a may handle inputs from the client device 200a.
  • the data processing module 206a may cause data to be written and stored in the memory device 204 based on the inputs from the client device 200b.
  • the data processing module 206a may rectrieve data stored in the memory device 204 and ouput the data to the client device 200a via the communication device 202.
  • the data permissions module 206b may determine, based on permissions data stored in the memory device, what data to output to the client device 200b and what format to output the data in (e.g. as a static variable, as a dynamic variable, and so forth). For example, a variable that is distilled for a particular user profile may be output as static. When the variable is enabled for the particular user profile, the variable may be output as dynamic.
  • the server device 200a may be representative of the cloud-based data management system 102.
  • the server device 200a may be representative of the application server 106.
  • the server device 200a may be representative of the data server 110.
  • the server device 200a may be representative of the external application server 116.
  • the memory device 204 may be representative of the database 108 and the processing device 206 may be representative of the data server 110.
  • the memory device 204 may be representative of the external database 118 and the processing device 206 may be representative of the external application server 116.
  • the database 108 and/or the external database 118 may be implemented as a block of memoiy in the memory device 204.
  • the memory device 204 may further store instructions that, when executed by the processing device 206, perform various functions with the data stored in the database 108 and/or the external database 118.
  • the client device 20% may be representative of the user device 104.
  • the client device 200b may be representative of the smartphone 112.
  • the client device 20% may be representative of the personal computer 114.
  • the memory device 210 may store application instructions that, when executed by the processing device 212, cause the client device 20% to perform various functions associated with the instructions, such as retrieving data, processing data, receiving input, processing input, transmitting data, and so forth.
  • the server device 200a and the client device 200b may be representative of various devices of the vaccination record management system 100.
  • Various of the elements of the vaccination record management system 100 may include data storage and/or processing capabilities. Such capabilities may be rendered by various electronics for processing and/or storing electronic signals.
  • One or more of the devices In the vaccination record management system 100 may include a processing device, for example, the cloud-based data management system 102, the user device 104, the smartphone 112, the personal computer 114, the external application server 116, and/or the external database 118 may include a processing device.
  • One or more of the devices in the vaccination record management system 100 may include a memory device.
  • the cloudbased data management system 102, the user device 104, the smartphone 112, the personal computer 114, the external application server 116, and/or the external database 118 may include the memoiy device.
  • the processing device may have volatile and/or persistent memory.
  • the memory device may have volatile and/or persistent memory.
  • the processing device may have volatile memory and the memory device may have persistent memory.
  • Memory in the processing device may be allocated dynamically according to variables, variable states, static objects, and permissions associated with objects and variables in the vaccination record management system 100. Such memory allocation may be based on instructions stored in the memory device. Memory resources at a specific device may be conserved relative to other systems that do not associate variables and other object with permission data for the specific device.
  • the processing device may generate an output based on an input, for example, the processing device may receive an electronic and/or digital signal.
  • the processing device may read the signal and perform one or more tasks with the signal, such as performing various functions with data in response to input received by the processing device.
  • the processing device may read from the memory device information needed to perform the functions. For example, the processing device may update a variable from static to dynamic based on a received input and a rule stored as data on the memory device.
  • the processing device may send an output signal to the memory device, and tire memory device may store data according to tire signal output by the processing device.
  • the processing device may be and/or include a processor, a microprocessor, a computer processing unit (CPU), a graphics processing unit (GPU), a neural processing unit, a physics processing unit, a digital signal processor, an image signal processor, a synergistic processing element, a field-programmable gate array (FPGA), a sound chip, a multi-core processor, and so forth.
  • processor a processor
  • CPU computer processing unit
  • GPU graphics processing unit
  • FPGA field-programmable gate array
  • processing unit may be used generically to refer to any or all of the aforementioned specific devices, elements, and/or features of tire processing device.
  • the memory device may be and/or include a computer processing unit register, a cache memory, a magnetic disk, an optical disk, a solid-state drive, and so forth.
  • the memory device may be configured with random access memory (RAM), read-only memory (ROM), static RAM, dynamic RAM, masked ROM, programmable ROM, erasable and programmable ROM, electrically erasable and programmable ROM, and so forth.
  • RAM random access memory
  • ROM read-only memory
  • static RAM dynamic RAM
  • masked ROM programmable ROM
  • programmable ROM erasable and programmable ROM
  • electrically erasable and programmable ROM and so forth.
  • “memory,” “memory component,” “memory device,” and/or “memory unit” may be used generically to refer to any or all of the aforementioned specific devices, elements, and/or features of the memory device.
  • Various of the devices in the vaccination record management system 100 may include data communication capabilities. Such capabilities may be rendered by various electronics for transmitting and/or receiving electronic and/or electromagnetic signals.
  • One or more of the devices in the vaccination record management system 100 may indude a communication device. e.g conference the communication device 202 and/or the communication device 208.
  • the cloud-based data manegement system 102, the user device 104, the smartphone 112, the personal computer 114, the application server 116, and/or the external database 118 may include a communication device.
  • the communication device may include, for example, a networking chip, one or more antennas, and/or one or more communication ports.
  • the communication device may generate radio frequency (RF) signals and transmit the RF signals via one or more of the antennas.
  • the communication device may receive and/or translate the RF signals.
  • the communication device may transceive the RF signals.
  • the RF signals may be broadcast and/or received by the antennas.
  • the communication device may generate electronic signals and transmit the RF signals via one or more of the communication ports.
  • the communication device may receive the RF signals from one or more of the communication ports.
  • the electronic signals may be transmitted to and/or from a communication hardline by the communication ports.
  • the communication device may generate optical signals and transmit the optical signals to one or more of the communication ports.
  • the communication device may receive the optical signals and/or may generate one or more digital signals based on the optical signals.
  • the optical signals may be transmitted to and/or received from a communication hardline by the communication port, and/or the optical signals may be transmitted and/or received across open space by the networking device.
  • the communication device may include hardware and/or software for generating and communicating signals over a direct and/or indirect network communication link.
  • the communication component may include a USB port and a USB wire, and/or an RF antenna with BluetoothTM programming installed on a processor, such as the processing component, coupled to the antenna.
  • the communication component may include an RF antenna and programming installed on a processor, such as the processing device, for communicating over a Wifi and/or cellular network
  • “communication device” “communication component,” and/or “communication unit” may be used generically herein to refer to any or all of the aforementioned elements and/or features of the communication component
  • Various of the elements in the vaccination record management system 100 may be referred to as a “server.”
  • Such elements may include a server device.
  • the server device may include a physical server and/or a virtual server.
  • the server device may include one or more bare-metal servers.
  • the bare-metal servers may be single-tenant servers or multiple tenant servers.
  • the server device may include a bare metal server partitioned into two or more virtual servers.
  • the virtual servers may include separate operating systems and/or applications from each other.
  • the server device may include a virtual server distributed on a cluster of networked physical servers.
  • the virtual servers may include an operating system and/or one or more applications installed on the virtual server and distributed across the cluster of networked physical servers.
  • the server device may include more than one virtual server distributed across a cluster of networked physical servers.
  • the term server may refer to functionality of a device and/or an application operating on a device.
  • an application server may be programming instantiated in an operating system installed on a memory device and run by a processing device.
  • the application server may include instructions for receiving, retrieving, storing, outputting, and/or processing data.
  • a processing server may be programming instantiated in an operating system that receives data, applies rules to data, makes inferences about the data, and so forth.
  • Servers referred to separately herein, such as an application server, a processing server, a collaboration server, a scheduling server, and so forth may be instantiated in the same operating system and/or on the same server device. Separate servers may be instantiated tn the same application or in different applications.
  • Data may be used to refer generically to modes of storing and/or conveying information. Accordingly, data may refer to textual entries in a table of a database. Data may refer to alphanumeric characters stored in a database. Data may refer to machine-readable code. Data may refer to images. Data may refer to audio. Data may refer to, more broadly, a sequence of one or more symbols. The symbols may be binary. Data may refer to a machine state that is computer-readable. Data may refer to human- readable text.
  • Various of the devices in the vaccination record management system 100 may include a user interface for outputting information in a format perceptible by a user and receiving input from the user, e.g., the user interface 214.
  • the user interface may include a display screen such as a light-emitting diode (LED) display, an organic LED (OLED) display, an active-matrix OLED (AMOLED) display, a liquid crystal display (LCD), a thin-film transistor (TFT) LCD, a plasma display, a quantum dot (QLED) display, and so forth.
  • the user interface may include an acoustic element such as a speaker, a microphone, and so forth.
  • the user interface may include a button, a switch, a keyboard, a touch- sensitive surface, a touchscreen, a camera, a fingerprint scanner, and so forth.
  • the touchscreen may include a resistive touchscreen, a capacitive touchscreen, and so forth.
  • the methods may be implemented by the data analysis system 100 and/or various elements of the data analysis system described above.
  • inputs indicated as being received in a method may be input at the client device 200b and/or received at the server device 200a.
  • Determinations made in the methods may be outputs generated by the processing device 206 based on inputs stared in the memory device 204.
  • Correlations performed in the methods may be executed by the correlation module 206a.
  • inference outputs may be generated by the inference module 206b.
  • Key date and/or actionable data may be stored in the knowledge database 204b.
  • Correlations between key data and actionable date may be stored in the knowledge database 204b.
  • Outputs generated in the methods may be output to the output database 204c and/or the client device 200b.
  • data described in the methods may be stored and/or processed by various elements of the data analysis system 100.
  • FIG. 3 illustrates a device schematic for various devices used in a vaccination record management system 300 for managing a vaccination record using a vaccination record application, such as a SYCVAC vaccination card application or the like.
  • the vaccination record management system 300 may comprise a digital interface 305, a visual indication module 310, a data repository 315, an encryption module 320, a user interface 325, and a processor 330.
  • the digital interface 305 may be configured to receive and scan a vaccination record associated with a user.
  • tire term “user” means a patient, a parent of a patient, a healthcare professional or provider, a government health agemy, a vaccination clinic, and the like.
  • the vaccination record may be a physical card, a digital card, a digital record, a medical certificate, or any other record containing vaccination information, including a vaccine type, a vaccine dose, and a vaccination date.
  • the digital interface 305 may comprise a high-resolution optical scanner 308 comprising image processing hardware 309 for precise and rapid scanning of the vaccination record.
  • the optical scanner 308 may be configured to scan the vaccination record, physically or electronically.
  • the digital interface 305 may conyrise a recognition system 307 that is configured to identify and associate the scanned vaccination record with a specific vaccine type and vaccine dose.
  • the recognition system 307 may be Integrated Into the digital interface 305 and utilize various methods, such as pattern recognition or barcode scanning, for determining the type and dosage of the vaccine.
  • the recognition system 307 may utilize optical character recognition (OCR) or natural language processing (NLP) to associate the scanned vaccination record with the specific type and dosage of the vaccine.
  • OCR optical character recognition
  • NLP natural language processing
  • the recognition system 307 may also utilize artificial intelligence or one or more machine learning algorithms to accurately identify and associate the scanned vaccination record with a specific type of vaccine and vaccine dose.
  • the digital interface 305 of the system 300 may support a multitude of languages, including seven or more, such as English, French, and German.
  • the visual indication module 310 may provide immediate feedback to the user and visually convey the successfol association of the scanned vaccination record with the specific vaccine information.
  • the recognition system 307 may process the information contained within the vaccination record or indicated thereon.
  • the visual indication module 310 may be configured to alter the color of the vaccination record displayed on the digital interface 305, transitioning it from red to green, to visually indicate the successful association of the scanned vaccination record with the specific vaccine or vaccine dose identified by the recognition system 307. Accordingly, the color transformation may provide the user with a visual signal of successful record-to-vaccine linkage so that the user can readily discern, at a glance, which of their vaccine doses have been accurately recorded within the application.
  • the system 300 may enhance user engagement and streamline the process of associating a vaccination record with a specific vaccine, thereby making vaccination record management more accessible and efficient for the user.
  • the data repository 315 may be configured to securely store, and manage the scanned vaccination record and its accompanying information and other information, such as user registration data, captured via the SYCVAC vaccination card application.
  • the data repository 315 may be communicatively linked to the encryption module 320 which may encrypt and decrypt all sensitive vaccine-related data, including personal and medical information, to safeguard it during transmission and storage.
  • the encryption module 320 may utilize various cryptographic techniques to transform the sensitive information into an unreadable format that may be impervious to unauthorized access while ensuring that only authorized users, with the necessary credentials and permissions, can decrypt and access the stored data.
  • the user interface 325 may be integrated with the digital interface 305 and may enable a user to interact with the SYCVAC vaccination card application.
  • the user interface 325 may display vaccine dose records, vaccine card associations, and user-specific vaccination information.
  • the user interface 325 may also comprise customizable display options to allow a user to organize and prioritize the presentation of their vaccine dose records and associated information based on their preferences. Additionally, the user interface 325 may be adaptable to support a multitude of languages, comprising at least seven or more distinct languages.
  • the processor 330 may perform various functions, such as data recognition, visual indication, data storage, coordinating data processing, user interactions, facilitating communication with external data repositories, and integration of various features of the application within the system 300. For instance, when a user scans their vaccination record using the digital interface 305, the processor 330 may utilize various algorithms, such as pattern recognition and barcode scanning algorithms, to process the data contained within or on the vaccination record. The processor 330 may use the scanned data to identify the type and dosage of the vaccine(s) administered and match the scanned vaccination record with a specific vaccine and vaccine dose, ensuring that the correct information is associated with the user's vaccination record.
  • various algorithms such as pattern recognition and barcode scanning algorithms
  • the processor 330 may be configured to generate a QR code encoding pertinent vaccination data, including the vaccine type, vaccine dose, or vaccination date determined from the specific vaccine information.
  • the processor 330 may enable users to navigate through various screens, access features, and interact with their vaccination records. For instance, the processor 330 may enable users to create accounts, add child profiles, update user and child profile information, view vaccination records, and switch between different view modes. In addition, the processor 330 may operate together with the visual indication module 310 to provide immediate feedback to the users.
  • the processor 330 may trigger a visual cue, which may be manifested through a transformation of the vaccination card’s color on the user interface 325 from red to green.
  • the processor 330 may store all or some of the vaccination data in the data repository 315 and organize, retrieve, and access the data when needed.
  • the processor 330 may comprise a hardware-based cryptographic processor which may be linked to the date encryption module 320 for performing end-to end encryption of the vaccine dose date.
  • the processor 330 may operate together with the encryption module 320 to encrypt or decrypt all sensitive vaccine dose date by managing encryption keys to ensure that only authorized users with the necessary credentials can decrypt and access the stored date.
  • the processor 330 may be configured to generate a personalized vaccination recommendation based on vaccination data of the user.
  • the personalized vaccination recommendation may be a vaccination schedule determined according to the vaccination record and a healto profile of the user.
  • the processor 330 may be programmed to execute a set of algorithms and operations configured to generate a personalized vaccination recommendation. For instance, the processor 330 may analyze the vaccination date of the user, which may contain a plethora of user-specific information, such as historical data on vaccines received and their respective dates. The processor 330 may process and analyze the user-specific information and extract relevant details such as vaccine types, dosage intervals, and dates of administration. Simultaneously, the processor 330 may generate a healto profile for the user.
  • the health profile may be generated based on various factors such as the user’s age, gender, underlying medical conditions, and any specific vaccination guidelines or recommendations based on the user's demographics.
  • the processor 330 may utilize one or more algorithms to create a personalized vaccination recommendation.
  • the algorithms may be utilized to generate a personalized vaccination recommendation based on the user’s immunization history, the recommended vaccination timeline for specific diseases, any booster shots or follow-up doses required to maintain immunity, and the like.
  • the personalized vaccination recommendation may comprise a user-centric vaccination schedule that is tailored to specific immunization requirements of the user to ensure that the recommended vaccinations are timely and in alignment with the user's health profile.
  • the processor 330 may be adapted to integrate geolocation data and cunent disease outbreak information to dynamically modify the user-centric vaccination schedule to ensure that the individual user receives timely vaccinations in response to local disease prevalence, travel plans, or potential exposure risks, which may in turn enhance the user's immunity in a geographically optimized manner.
  • FIG. 4A illustrates a login screen of a SYCVAC vaccination card application 400, according to an embodiment
  • the login screen of the SYCVAC vaccination card application 400 may enhance the user experience by addressing various aspects of user registration and login proc s.
  • the user can register by entering essential information such as their name, email, and password.
  • the registration process may serve as a gateway to vaccination record management by allowing a user to create a personalized account
  • the user may provide various information, such as their full name, email address, and a secure password.
  • the application may also include optional fields for additional information.
  • the application 400 may accommodate individual choices and circumstances by, for example, providing multiple login options. For example, a user can opt for traditional email and password authentication, ensuring secure access to their account with stringent password security measures. Alternatively, the user may choose to log in using their Facebook account or other existing social media identity.
  • FIG. 4B illustrates a password reset screen of the SYCVAC vaccination card implication 400, featuring a designated box for users to input their email address, according to an embodiment
  • the application 400 may comprise a password reset system or process.
  • the user may click a "Forgot password?” link to securely reset their password, which may involve the user receiving a reset link via email and following provided instructions.
  • FIG. 4C illustrates an interface for editing a user profile within the SYCVAC vaccination card amplication 400, according to an embodiment
  • the SYCVAC vaccination card application 400 may grant the user access to a personalized user profile within the application 400.
  • the profile may serve as a digital identity, enabling the user to interact with various features and functionalities of the application.
  • the user may personalize their profile with information such as their full name, email address, and optional details like contact information or profile picture.
  • the user may also easily edit and update their profile information as needed.
  • the application 400 may enable the user to manage their privacy settings and control what information is visible to others to ensure the confidentiality of their vaccination records and personalized details if desired.
  • FIG. 4D illustrates a feature of the SYCVAC vaccination card application 400 that allows parents and guardians to manage vaccination records for their children, according to an embodiment.
  • parents can create a child profile upon registration by entering essential information such as the child's photo, name, age, identification (ID), school affiliation, and gender.
  • This feature may accommodate changes in a child’s details, allowing parents to keep records current and accurate and efficiently add new child profiles as their families grow, streamlining the process and ensuring accurate record-keeping.
  • the child profiles may be repositories of personal information and serve as hubs for tracking vaccinations in order to provide parents with convenient access to their children's vaccination records through list or calendar views.
  • FIG. 4E itlustrates a vaccination record displayed in a list format within the SYCVAC vaccination card application 400, according to an embodiment
  • This format may enhance the ability of users to monitor vaccination schedules and adherence, ultimately aiding in their vaccination management, according to an embodiment.
  • the SYCVAC vaccination card application 400 may provide a user with comprehensive vaccination record management capabilities. The user may easily access, review, and update their vaccination records through the application 400. Specifically, the user may view the details of each vaccine dose, check vaccination dates, and ensure compliance with recommended vaccination schedules. In addition to managing their vaccination records, the user can switch between view modes at their convenience. To cater to varying user preferences and needs, the SYCVAC vaccination card application 400 may provide multiple view modes for vaccination record tracking. For instance, instead of the list format, a user may opt for a calendar view.
  • FIG. 4F illustrates a vaccination record presented in a calendar view within the SYCVAC vaccination card application 400, according to an embodiment
  • This view can enhance users* ability to monitor vaccination schedules and adherence, providing a convenient way to manage vaccinations, according to an embodiment.
  • the application's calendar view may be particularly beneficial for a user who prefers a visual representation of their vaccination schedule. By eliciting on a "Calendar" icon, the user may access a clear and organized calendar interface displaying essential vaccination dates. This feature may also provide parents managing their children's vaccinations or individuals tracking multiple vaccines for various pathogens.
  • FIG. 4G illustrates an interface of the SYCVAC vaccination card application 400 for enabling school administrators to efficiently access and review registered children's information and vaccination schedules through the application, according to an embodiment.
  • the administrators can log in using provided credentials, including email and password, via an app control panel. Once logged in, an administrator may gain access to a list of registered children and can easily retrieve and review their information and vaccination schedules.
  • the inclusion of a search bar feature may expedite the process of locating specific children within the application 400.
  • school administrators may have the flexibility to switch between view modes, such as calendar view, and navigate child profiles to examine information and vaccination records.
  • FIG. 5 illustrates a red card 501 within a vaccination record application 500, according to an embodiment.
  • the red card 501 may comprise a concise and easily readable representation of an individual's health states in the context of COVID-19.
  • the red card 501 may display essential personal information, such as the patient's name, date of birth, gender, and a unique identification number. This information may be utilized to ensure the card is accurately linked to the individual it pertains to.
  • the red card 501 may also comprise a result section, which indicates whether the individual has tested positive or negative for a particular health condition, such as COVID-19. This result may be used by individuals and healthcare professionals, as it guides the necessary actions to be taken for their health and safety.
  • the red card 501 may comprise information about the healthcare professional involved, including their name, the date of the test or vaccination, the specific location where the test or vaccination was administered, and their professional signature. These details may be used to verify the legitimacy of the card to ensure that it accurately represents the healthcare sendee provided.
  • the red card 501 may comprise a QR code that can be scanned and linked to a database that stares more comprehensive health records or up-to-date COVID-19 testing and vaccination information.
  • the QR code may provide a quick and contactless way for relevant authorities to access and confirm the individual's health status in realtime.
  • FIG. 6A illustrates a vaccination record application 600 featuring an "Add Child” button 603, which parent users can click on to create a profile for their child and monitor the child's vaccination records, which are typically added by healthcare entities like hospitals.
  • This user-friendly feature may simplify the process of adding and managing child profiles.
  • FIG. 6B illustrates a layout of a vaccination record application 600 that provides users with the capability to share their immunization records conveniently through email, WhatsApp, and various other communication platforms. This feature may enable users to securely transmit their vaccination data to healthcare providers, authorities, or other individuals. In this regard, this feature may facilitate data sharing and the efficient management of vaccination records.
  • FIG. 7 illustrates a layout of a vaccination record application 700 that allows patients and healthcare providers to log into the system.
  • the application may be versatile, as it can be downloaded onto either a mobile device or a computer. This adaptability may enable patients to conveniently access their digital vaccine records on their preferred mobile device, while healthcare providers have the same accessibility, making the process seamless for all users.
  • FIG. 8 illustrates a layout within a vaccination record application 800 where healthcare providers can conveniently record the number of vaccine doses administered, according to an embodiment. For example, this may be achieved by entering the patient's ID number, which may in turn improve the process of updating vaccination records and ensure accurate documentation of vaccine administrations.
  • FIG. 9 is a flow diagram of a method (900) for managing a vaccination record using a vaccination record application.
  • the process may begin with using the digital interface and optical scanner for submitting and scanning the vaccination record (905).
  • the vaccination record may be a physical card or a digital card containing Information regarding a vaccine dose administered to the user.
  • the digital interface may provide step-by-step guidance or instructions to the user during the scanning process of the vaccination record.
  • the next step (910) may comprise utilizing the recognition system, which may be integrated with the digital interface, to associate the scanned vaccination record with specific vaccination information, including a vaccine type, a vaccine dose, and a vaccination date from the scanned verification record.
  • the recognition system may utilize optical character recognition (OCR), natural languageye processing (NLP), artificial intelligence, or a machine learning algorithm to associate the scanned vaccination record with specific vaccination information, thereby linking the scanned vaccination record with the specific vaccine or vaccine dose.
  • OCR optical character recognition
  • NLP natural languageye processing
  • artificial intelligence or a machine learning algorithm
  • the next step (915) may comprise using a dynamic feedback module for providing real-time feedback to the user in order to confirm the correct association.
  • Providing real-time feedback to the user may comprise utilizing a color coding, a textual prompt, or an audio cue to confirm the association of the scanned vaccination record with the specific vaccine or vaccine dose identified by the recognition system.
  • step (915) may comprise altering the color of the vaccination record displayed on the digital interface, via the visual indication module, where altering the color may comprise transitioning the color from red to green to visually indicate the successful association of the scanned vaccination record with the specific information identified by the recognition system.
  • step (915) may comprise utilizing the dynamic feedback module to deliver audio cues via an audio device, such as a speaker of a mobile device, where the audio cues may be used to audibly confirm the successful association of the scanned vaccination record with the specific vaccine or vaccine dose identified by the recognition system, thereby enhancing user accessibility for those with visual impairments or in situations where visual feedback may not be practical.
  • an audio device such as a speaker of a mobile device
  • step (920) may comprise establishing a secure and scalable data repository interface within the application.
  • the data repository may comprise redundant hardware architecture to provide continuous connectivity to various data storage solutions, including cloud-based databases, healthcare information systems, and blockchain-based ledgers to ensure the storage of encrypted vaccination records and associated data.
  • step (925) may comprise utilizing the encryption module to encrypt sensitive information captured from the scanned vaccination record.
  • the encryption process may begin when the vaccination record information, such as the specific vaccination information, is generated or received within the application or is prepared for transmission or storage.
  • the specific vaccination information may include details of vaccine doses administered, dates, and associated metadata.
  • the specific vaccination information may be considered sensitive and confidential and may therefore be encrypted via the encryption module.
  • the encryption module may convert the plain text specific vaccination information into ciphertext using various encryption algorithms, such as Advanced Encryption Standard (AES) or the like.
  • AES Advanced Encryption Standard
  • the encryption process may comprise performing a mathematical transformation that renders the specific vaccination information unreadable without the corresponding decryption key.
  • the encryption module may perform decryption.
  • the encryption module may utilize the same cryptographic processors to efficiently reverse the encryption process, converting the ciphertext back into plain text.
  • the decryption process may require the use of a decryption key, which may be securely stored and managed by the application.
  • step (930) may comprise generating, via the processor, a personalized vaccination recommendation based on the specific vaccination information.
  • Step (930) may comprise utilizing the processor to analyze the vaccination data of the user, which may contain historical data on vaccines received and their respective dates.
  • the processor may perform data mining and analysis on the information and extract relevant details such as vaccine types, dosage intervals, and dates of administration.
  • the processor may analyze and generate a health profile of the user.
  • the health profile may be generated based on factors, such as the user’s age, gender, underlying medical conditions, and any specific vaccination guidelines or recommendations based on the user's demographics.
  • step (935) may comprise utilizing one or more algorithms, executed via the processor, to create a personalized vaccination recommendation based on the user's immunization history, the recommended vaccination timeline for specific diseases, any booster shots or follow-up doses required to maintain immunity, and the like.
  • the personalized vaccination recommendation may be a personalized vaccine schedule that outlines when the user should receive particular vaccines or booster doses based on their unique health status and vaccination history.
  • step (935) may comprise, upon a successful scanning of the vaccination record by the recognition system, utilizing the processor to generate a QR code encoding pertinent vaccination data, wherein the pertinent vaccination data comprises certain information such as the vaccine type, vaccine dose, or vaccination date determined from the specific vaccine information.
  • step (935) may also comprise providing the user with an analytics and reporting module, via the user interface.
  • the analytics and reporting module may enable a user to generate a comprehensive vaccination report, a compliance summary, and a historical vaccination trend analysis, which in turn may aid the user make informed decisions and more effectively manage their health.
  • step (935) may further comprise facilitating interoperability through a communication module of the vaccination record application by integrating with healthcare providers, government health agencies, vaccination clinics, and health information exchanges.
  • the communication module may establish a secure network connection with healthcare providers, government health agencies, vaccination clinics, or health information exchanges to transmit the QR code generated by the processor.
  • the communication module may establish a secure connection with the mobile devices of the user's designated contacts to transmit the QR code generated by the processor.
  • the communication module may establish such secure connections using an encrypted communication protocol and/or an authenticated access method.
  • the communication module may enable bidirectional data sharing, real-time updates, and remote vaccination verification.
  • the communication module may be implemented using a network interface, cryptographic processor, a secure hardware component, or any other hardware component to establish and maintain a secure connection with various external components, including healthcare providers, government health agencies, vaccination clinics, and health information exchanges (HIEs).
  • the communication module may utilize various authentication protocols that rely on secure cryptographic keys and certificates. Bidirectional data exchange may then be facilitated to allow healthcare providers and agencies validate vaccination statuses, transmit real-time updates, and perform remote vaccination verifications.
  • the communication module may interact with blockchain nodes, initiating transactions for recording vaccine administrations and retrieving historical vaccination data.
  • a feature illustrated in one of the figures may be the same as or similar to a feature illustrated in another of the figures.
  • a feature described in connection with one of the figures may be the same as or similar to a feature described in connection with another of the figures.
  • the same or similar features may be noted by the same or similar reference characters unless expressly described otherwise. Additionally, the description of a particular figure may refer to a feature not shown in the particular figure. The feature may be Illustrated in and/or further described in connection with another figure.
  • an example described as including A, B, C, and D is an example that includes A, includes B, includes C, and also includes D.
  • “or” forms a list of elements, any of which may be included.
  • an example described as including A, B, C, or D is an example that includes any of the elements A, B, C, and D.
  • an example including a list of altematively-inclusive elements does not preclude other examples that include various combinations of some or all of theretematively-inclusive elements.
  • An example described using a list of altematively-inclusive elements includes at least one element of the listed elements.
  • an example described using a list of altematively-inclusive elements does not preclude another example that includes all of the listed elements. And. an example described using a list of altematively-inclusive elements does not preclude another example that includes a combination of some of the listed elements.
  • “and/or” forms a list of elements inclusive alone or in any combination.
  • an example described as including A, B, C, and/or D is an example that may include: A alone; A and B; A, B and C; A, B, C, and D; and so forth.
  • the bounds of an “and/or” list are defined by tile complete set of combinations and permutations for the list.

Landscapes

  • Engineering & Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Public Health (AREA)
  • Primary Health Care (AREA)
  • Epidemiology (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Biomedical Technology (AREA)
  • Bioethics (AREA)
  • Software Systems (AREA)
  • Databases & Information Systems (AREA)
  • Chemical & Material Sciences (AREA)
  • Bioinformatics & Cheminformatics (AREA)
  • Medicinal Chemistry (AREA)
  • Pathology (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

Sont décrits des exemples de systèmes de gestion de dossier de vaccination, comprenant une interface numérique, un système de reconnaissance, un module d'indication visuelle, un référentiel de données, un module de chiffrement de données et un processeur. L'interface numérique peut être configurée pour balayer un dossier de vaccination, et le système de reconnaissance peut être intégré à l'interface numérique et configuré pour identifier et associer le dossier de vaccination balayé à des informations de vaccin spécifiques. Le module d'indication visuelle peut être configuré pour indiquer visuellement l'association réussie du dossier de vaccination balayé avec les informations de vaccin spécifiques par le système de reconnaissance. Le référentiel de données peut être configuré pour stocker des données chiffrées relatives aux informations de vaccin spécifiques, et le module de chiffrement de données peut être configuré pour chiffrer les informations de vaccin spécifiques pour une transmission et un stockage sécurisés dans le référentiel de données. Le processeur peut être configuré pour générer une recommandation de vaccination sur la base d'un dossier de vaccination de l'utilisateur.
PCT/US2023/078738 2023-11-03 2023-11-03 Systèmes de gestion de dossier de vaccination Pending WO2025095979A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/US2023/078738 WO2025095979A1 (fr) 2023-11-03 2023-11-03 Systèmes de gestion de dossier de vaccination

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2023/078738 WO2025095979A1 (fr) 2023-11-03 2023-11-03 Systèmes de gestion de dossier de vaccination

Publications (1)

Publication Number Publication Date
WO2025095979A1 true WO2025095979A1 (fr) 2025-05-08

Family

ID=95581435

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2023/078738 Pending WO2025095979A1 (fr) 2023-11-03 2023-11-03 Systèmes de gestion de dossier de vaccination

Country Status (1)

Country Link
WO (1) WO2025095979A1 (fr)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060218010A1 (en) * 2004-10-18 2006-09-28 Bioveris Corporation Systems and methods for obtaining, storing, processing and utilizing immunologic information of individuals and populations
JP2018073068A (ja) * 2016-10-27 2018-05-10 株式会社湯山製作所 電子カルテシステム及び電子カルテプログラム
US20210343387A1 (en) * 2017-01-17 2021-11-04 Kaleo, Inc. Medicament delivery devices with wireless connectivity and event detection
US20220208390A1 (en) * 2020-12-31 2022-06-30 Change Healthcare Holdings, Llc Vaccination record
US20220270727A1 (en) * 2021-02-22 2022-08-25 SecondOpinionExpert, Inc. Method and apparatus for generating an electronic medical badge
US20230326611A1 (en) * 2022-04-06 2023-10-12 Temperature SafeNet, Inc. Systems and methods for controlling illness risk information

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060218010A1 (en) * 2004-10-18 2006-09-28 Bioveris Corporation Systems and methods for obtaining, storing, processing and utilizing immunologic information of individuals and populations
JP2018073068A (ja) * 2016-10-27 2018-05-10 株式会社湯山製作所 電子カルテシステム及び電子カルテプログラム
US20210343387A1 (en) * 2017-01-17 2021-11-04 Kaleo, Inc. Medicament delivery devices with wireless connectivity and event detection
US20220208390A1 (en) * 2020-12-31 2022-06-30 Change Healthcare Holdings, Llc Vaccination record
US20220270727A1 (en) * 2021-02-22 2022-08-25 SecondOpinionExpert, Inc. Method and apparatus for generating an electronic medical badge
US20230326611A1 (en) * 2022-04-06 2023-10-12 Temperature SafeNet, Inc. Systems and methods for controlling illness risk information

Similar Documents

Publication Publication Date Title
US20240289715A1 (en) Smart label devices, systems, and methods
US20250124172A1 (en) Cloud-based system for protecting sensitive information in shared content
US9619771B2 (en) Systems and methods for digital workflow and communication
US20200161003A1 (en) Cloud based viewing, transfer and storage of medical data
US20210327548A1 (en) Storing, authenticating, and transmitting health data
US20140114672A1 (en) Cloud based viewing, transfer and storage of medical data
US20180032757A1 (en) Health Status Matching System and Method
US9258297B2 (en) Methods, devices, and mediums for securely sharing restricted content
US20210174914A1 (en) Procedure for the global unified registration and universal identification of donors
US20160328523A1 (en) System and method for documenting patient information
US8667290B2 (en) Efficient, high volume digital signature system for medical and business applications
US20150213197A1 (en) Event Based Tracking, Health Management, and Patient and Treatment Monitoring System
US12183440B2 (en) Computer system, method, and device for verifying an immunization status
WO2025034498A1 (fr) Systèmes et procédés de sécurisation de données lors d'un transit entre des systèmes disparates et pendant un repos
CN106104475A (zh) 使用外部源的用户设置管理
Sabnis et al. Opportunities and challenges: Security in ehealth
EP4136607A1 (fr) Stockage, authentification, et transmission de données de santé
US20240087728A1 (en) Methods, systems, apparatuses, and devices for facilitating creating labels for labeling intravenous infusion lines
WO2025095979A1 (fr) Systèmes de gestion de dossier de vaccination
Benaich et al. Pioneering the Security of EHRs Using an Immersive Blockchain Conceptual Framework
US20230307147A1 (en) Patient hub
US20170091396A1 (en) System and method for providing access to electronically stored medical information
Khatoon et al. Integrating OAuth and aadhaar with e-health care system
US20240380433A1 (en) Sharing Secure User Information Using Near-Field Communication
Walid Cloud-Based Encrypted EHR System With Semantically Rich Access Control

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23957866

Country of ref document: EP

Kind code of ref document: A1