A pre-hospital and in-hospital emergency data two-way intercommunication system and method based on wristband identification
Patent Information
- Application Number
- CN202610848202.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2026-06-12
- Publication Date
- 2026-09-15
- Estimated Expiration
- 2046-06-12
AI Technical Summary
[0003]本发明旨在提供一种基于腕带标识的院前院内急救数据双向互通方法,以解决现有技术中院前与院内急救数据无法高效、可靠、连续双向互通的问题,实现以唯一腕带编码为索引的全程数据关联、可靠上传与时间轴精确对齐
本发明在院前急救数据包上传环节引入了实时传输可靠性指数的计算与条件传输机制。该指数基于当前无线信号接收强度指示值、环境本底噪声门限、可用上行带宽和预估传输所需带宽进行量化评估,仅当
时才启动上传,否则将数据包暂存于本地加密缓存区并持续监测网络直至满足条件。这种动态可靠性评估方案避免了在弱信号或低带宽环境下盲目传输导致的数据损坏或丢失,确保院前急救数据包能够在网络条件满足要求时完整、准确地到达院前急救数据中心,从而保障后续院内查询时数据的完整性与可用性,显著降低了因网络不稳定造成的院前数据流失风险。本发明在患者转归后的数据回传与归档过程中,引入了基于同一类型共同事件的时间校准偏移量
计算模型。该模型通过提取院前与院内共有的事件(如实测生理参数记录时间)计算平均时间差,并将院前数据包中所有时间戳统一加上
进行校准,再将校准后的院前数据与院内救治数据按时间顺序合并。这一方案消除了院前终端与院内服务器之间由于系统时钟不同步导致的系统性时间偏差,使得合并后的全流程救治档案能够真实反映患者从院前到院内的完整救治时序,避免了因时间错位导致的事件因果倒置或评估失真,为后续的质控分析、临床回顾与医疗文书归档提供了准确的时间轴基础。
Smart Images

Figure CN122417344B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of medical information data processing technology, specifically to a two-way data exchange system and method for pre-hospital and in-hospital emergency care based on wristband identification. Background Technology
[0002] In the process of connecting pre-hospital emergency care with in-hospital emergency care, patient injury information often relies on paper documents or verbal communication, leading to information gaps, duplicate data collection, and low efficiency. Current technologies suffer from the following issues: pre-hospital emergency personnel collect patient information by handwriting or simple electronic records, which is then re-entered by triage nurses upon the patient's arrival at the hospital. This not only delays treatment time but also increases the risk of medical complications due to information errors. Some improvement solutions attempt to identify patients using barcodes or RFID tags, but these fail to establish a complete two-way data exchange link between pre-hospital and in-hospital care, particularly in situations with unstable wireless networks in the pre-hospital environment, and in cases of data misordering due to inconsistencies in the timelines of pre-hospital and in-hospital events. Existing technologies lack a dynamic evaluation mechanism for data transmission reliability; direct transmission under weak signal or insufficient bandwidth results in high error rates and data loss. Furthermore, there is an inherent discrepancy between the timestamps recorded in the pre-hospital system and those in the in-hospital system. Directly splicing files can lead to disordered sequences of critical treatment events, affecting the review and quality assessment of the treatment process. Therefore, a bidirectional data exchange method is needed that can ensure reliable transmission of pre-hospital data and accurately align the timelines of pre-hospital and in-hospital events. Summary of the Invention
[0003] This invention aims to provide a method for bidirectional data exchange between pre-hospital and in-hospital emergency care based on wristband identification, in order to solve the problem that pre-hospital and in-hospital emergency care data cannot be exchanged efficiently, reliably, and continuously in the prior art, and to achieve full-process data association, reliable uploading, and precise timeline alignment with a unique wristband code as the index.
[0004] The objective of this invention can be achieved through the following technical solutions: A method for bidirectional data exchange between pre-hospital and in-hospital emergency care based on wristband identification includes: acquiring a disposable passive identification wristband selected by emergency personnel according to the patient's initial injury level; the wristband has a globally unique QR code pre-printed on its surface, and the wristband color corresponds to a specific injury level; in a pre-hospital emergency care scenario, scanning the QR code with an emergency mobile terminal to obtain the wristband code; recording the patient's basic information, physiological parameters, preliminary diagnosis, and implemented emergency measures collected on-site into the emergency electronic medical record; and binding the emergency electronic medical record with the wristband code to generate a bound pre-hospital emergency care data package; in an in-hospital emergency triage scenario, using an emergency triage terminal... Scanning the QR code and reading the wristband code automatically initiates a query request to the pre-hospital data platform, retrieving and displaying the bound pre-hospital emergency data package in real time. In in-hospital care scenarios, the hospital information system uses the wristband code as a global primary key, automatically associating and storing all in-hospital treatment records with the wristband code. In patient outcome scenarios, the hospital information system automatically extracts key treatment summaries and outcome information, proactively pushing the in-hospital treatment data package containing the outcome information back to the emergency center data platform through a standardized data exchange interface. This data is then archived and integrated with the pre-hospital emergency data package to form a complete patient treatment record. By using wristband codes throughout the pre-hospital and in-hospital processes, the system achieves unique patient identification and two-way data communication, effectively eliminating information silos and improving emergency response efficiency.
[0005] When obtaining a disposable passive identification wristband selected by emergency personnel based on the patient's initial injury level, the personnel conduct a rapid on-site assessment of the patient according to a pre-set triage system, classifying patients into four levels: critical, severe, mild, and fatal. Based on the assessment results, a disposable passive identification wristband of the corresponding color is selected from a wristband storage unit with color codes following international standards: red corresponds to critical level, yellow to severe level, green to mild level, and black to fatal level. The selected wristband is then securely worn on the patient's wrist, completing the physical identification and binding of the patient's identity to their injury level. Color coding enables intuitive identification of injury levels, facilitating rapid pre-hospital and in-hospital coordination.
[0006] When generating the bound pre-hospital emergency data package, the scanning function of the emergency mobile terminal is activated to capture an image of the QR code on the surface of the disposable passive identification wristband; the captured QR code image is decoded to extract a unique wristband code string; the wristband code is displayed in the user interface of the emergency mobile terminal, and a blank emergency electronic medical record template indexed by the wristband code is automatically created; the emergency personnel enter or acquire the patient's basic information, continuous physiological parameter waveforms and values, preliminary injury diagnosis text description, and executed emergency measures in the form fields corresponding to the blank emergency electronic medical record template; when the emergency personnel confirm the completion of the data entry and submit it, the emergency mobile terminal logically associates all the entered data with the wristband code and encapsulates it into a structured data package, namely the bound pre-hospital emergency data package; the bound pre-hospital emergency data package is uploaded in real time to a designated storage area of the pre-hospital emergency data center via a wireless network, with the wristband code as the primary index key. After generating the bound pre-hospital emergency data package, the emergency mobile terminal calculates the real-time transmission reliability index of the current link through the built-in network quality assessment module. The real-time transmission reliability index The calculation formula is:
[0007] in: This is the current wireless signal strength indicator value, in dBm. This is the preset ambient background noise threshold, in dBm. This represents the currently available uplink bandwidth, in kbps. The estimated bandwidth required for the transmission of the pre-hospital emergency data packet, in kbps; if and only if At that time, the emergency mobile terminal immediately initiates the upload operation of the pre-hospital emergency data packet; if The emergency mobile terminal will temporarily store the pre-hospital emergency data packet in a local encrypted cache and continuously monitor the network status until... Automatic resume transmission after recovery. By introducing a transmission reliability index to dynamically assess network quality, it ensures that pre-hospital data is not lost in weak network environments, achieving reliable uploading. Specifically, it comprehensively evaluates the degree to which wireless link quality and bandwidth resources guarantee data transmission success rate. In the formula, since both signal strength and noise threshold are measured in dBm, their ratio essentially characterizes the strength of the current signal relative to the ambient noise floor, i.e., the signal-to-noise ratio (SNR). The larger this ratio, the clearer the signal and the higher the transmission reliability. The bandwidth factor is calculated using a logarithmic function because, according to the information transmission principle revealed by Shannon's formula, channel capacity and bandwidth have a logarithmic relationship, rather than a simple linear one. When transmitting fixed-size data packets, the gain in successful transmission guarantee brought by the increase in available bandwidth diminishes marginally, and the logarithmic function accurately simulates this physical characteristic. Therefore, by combining the SNR factor and bandwidth gain factor through a product model, when either condition deteriorates, it will linearly or logarithmically lower the overall reliability index, thus providing a comprehensive judgment threshold that conforms to communication principles for transmission decisions.
[0008] In an in-hospital emergency triage scenario, when a patient arrives at the hospital's emergency triage station, medical staff use the emergency triage terminal's scanner to scan the QR code on the patient's wristband. Based on this wristband code, a query request is automatically initiated to the pre-hospital data platform to obtain and display the bound pre-hospital emergency data package in real time. The patient's wristband is scanned by the emergency triage terminal's scanner. The terminal's decoding module decodes the QR code to obtain the wristband code. The terminal's communication module automatically constructs a standardized query request message containing the wristband code and sends it via the hospital's intranet to the pre-hospital-in-hospital data interface server deployed at the hospital's information boundary. The pre-hospital-in-hospital data interface server receives the standardized query request message, parses the wristband code, and uses this code as an index to initiate a data retrieval in the storage area of the pre-hospital emergency data center. The pre-hospital emergency data center returns a pre-hospital emergency data packet bound to the wristband code. The pre-hospital-in-hospital data interface server forwards the received bound pre-hospital emergency data packet back to the emergency triage terminal. The display interface of the emergency triage terminal parses and renders the key information in the bound pre-hospital emergency data packet, displays it visually, and automatically triggers the creation or association of an emergency medical record identified by the wristband code in the hospital information system. By scanning the code to retrieve information, triage personnel can obtain complete pre-hospital information without repeated data entry, shortening triage time and improving reception efficiency.
[0009] In hospital settings, the hospital information system uses the wristband code as a global primary key to automatically associate and store all medical records generated within the hospital with the wristband code. These records include examination results, treatment records, medication information, and nursing records. Within its database, the hospital information system establishes a treatment context with the wristband code as the core index for each visit confirmed through the emergency triage process. When a doctor issues a medical order at their workstation, the hospital information system's order processing module automatically associates the order record with the wristband code in the current treatment context. When a nurse performs a nursing procedure and records it at their workstation, the hospital information system's nursing record module automatically associates the nursing record with the wristband code. When the laboratory information system or image archiving and communication system generates a patient's laboratory or image report, the system uses inter-system interfaces to associate the report's unique identifier with the treatment record corresponding to the wristband code in the hospital information system. All association operations are automatically completed by the system backend, and the generated structured or unstructured medical data is stored in the hospital's clinical data warehouse with the wristband code as the key index field. By using wristband coding as a global primary key, all medical records within the hospital are automatically linked, ensuring data integrity and traceability and avoiding errors from manual data entry.
[0010] When establishing a treatment context with the wristband code as the core index for a visit confirmed through the emergency triage process in its database, the emergency triage terminal, after successfully acquiring pre-hospital data, sends a patient registration request to the patient management service of the hospital information system. This request carries the wristband code, basic patient information, and visit time. Upon receiving the request, the patient management service first checks the entire system for an active visit record with the wristband code as the primary index. If no record exists, a new visit record is created for the patient, and the wristband code is written into the primary index field of that record. The record's status is marked as "Emergency Visit in Progress," thus establishing the treatment context. If an active record already exists, the new treatment activity is associated with the existing treatment context to ensure data continuity. Through uniqueness checks and context reuse mechanisms, data duplication or conflict is avoided, ensuring the continuity and consistency of patient treatment records.
[0011] When a patient's full-process treatment record is created, a data feedback process is triggered when the patient's treatment status in the hospital information system changes to "discharged" or "transferred." The data extraction module of the hospital information system automatically extracts key information from all medical records associated with the wristband code according to preset summary rules. This key information includes the final diagnosis, major surgical procedures, important positive test results, discharge medication recommendations, and patient outcome. The data extraction module encapsulates the extracted key information according to the standardized data format defined by the emergency center data platform, generating a structured in-hospital treatment data package. The interface service module of the hospital information system pushes the in-hospital treatment data package to the data receiving endpoint designated by the emergency center data platform by calling a pre-configured application programming interface. After receiving the in-hospital treatment data package, the data processing service of the emergency center data platform parses out the wristband code and uses this code as a key to retrieve and match the corresponding pre-hospital emergency data package. The in-hospital treatment data package and the pre-hospital emergency data package are then merged and logically associated in chronological order. The emergency center data platform's data processing service extracts key event sequences marked with absolute timestamps from pre-hospital emergency data packets and in-hospital treatment data packets; and defines time calibration offsets. The calculation formula is:
[0012] in: The number of the same type of events shared by pre-hospital and in-hospital patients; The first recorded by the hospital's internal system The time of occurrence of a common event, in seconds; The first recorded by the pre-hospital system The timestamps of the same common event are displayed in seconds; the data processing service adds all timestamps in the pre-hospital emergency data packet to... A unified calibration is performed, and then the calibrated pre-hospital data packets and in-hospital treatment data packets are merged in chronological order to form a continuous timeline-based full-process treatment record with the wristband code as the global identifier. This record is stored in a unified patient record database, forming a complete patient treatment record spanning both pre-hospital and in-hospital stages. Through time calibration and automatic merging, clock discrepancies between pre-hospital and in-hospital systems are eliminated, generating accurate and traceable full-process treatment records, providing comprehensive data support for medical quality assessment and scientific research.
[0013] The data extraction module of the hospital information system automatically extracts key information from all medical records associated with the wristband code according to preset summarization rules. These rules define the data fields to be extracted, the data source table, and the extraction logic for free text. For structured data fields, the module directly queries the specified table in the database to retrieve records associated with the wristband code and extracts the values of the specified fields. For unstructured text data, the module uses a natural language processing engine to parse the medical records and surgical records, identifying and extracting entities and events that conform to the summarization rules. Entities include disease names, surgical names, and drug names; events include treatment actions and examination findings. All extracted structured field values and entity and event information parsed from the text are then populated using a standardized data format template. By combining structured data processing with natural language processing, high-quality summaries are automatically generated, reducing the burden of manual data entry and ensuring the accuracy of data extraction.
[0014] The standardized data exchange interface is implemented using an application programming interface based on the Health Level 7 Rapid Medical Interoperability Resource Standard. This standardized data exchange interface defines the resource types, data elements, and exchange protocols for pre-hospital emergency data packets and in-hospital treatment data packets. The HL7FHIR standard is adopted to ensure interoperability and scalability between different systems and reduce integration costs.
[0015] A two-way data exchange system for pre-hospital and in-hospital emergency care based on wristband identification includes a memory, a processor, and a computer program stored in the memory and running on the processor. When the processor executes the computer program, it implements the steps of the aforementioned two-way data exchange method for pre-hospital and in-hospital emergency care based on wristband identification. Through hardware and software collaboration, this method is integrated into a practical system to achieve fully automated data exchange throughout the entire process.
[0016] The beneficial effects of this invention are: This invention introduces a real-time transmission reliability index in the pre-hospital emergency data packet uploading process. The calculation and conditional transmission mechanism of the index. This index is quantitatively evaluated based on the current wireless signal received strength indication, ambient noise floor threshold, available uplink bandwidth, and estimated transmission bandwidth, and is applied only when... Uploading is only initiated when conditions are met; otherwise, data packets are temporarily stored in a local encrypted cache, and the network is continuously monitored until the conditions are met. This dynamic reliability assessment scheme avoids data corruption or loss caused by blind transmission in weak signal or low bandwidth environments, ensuring that pre-hospital emergency data packets can arrive at the pre-hospital emergency data center completely and accurately when network conditions meet the requirements. This guarantees the integrity and availability of data during subsequent in-hospital queries and significantly reduces the risk of pre-hospital data loss due to network instability. In the data return and archiving process after patient outcomes, this invention introduces a time calibration offset based on common events of the same type. The computational model calculates the average time difference by extracting events common to both pre-hospital and in-hospital use (such as the recording time of measured physiological parameters), and adds a uniform timestamp to all timestamps in the pre-hospital data packet. The data is calibrated, and then the calibrated pre-hospital data is merged with the in-hospital treatment data in chronological order. This approach eliminates the systematic time discrepancy caused by the asynchrony of system clocks between the pre-hospital terminal and the in-hospital server, ensuring that the merged full-process treatment record accurately reflects the complete treatment sequence from pre-hospital to in-hospital care. This avoids causal reversal or distorted assessments caused by time misalignment, providing an accurate timeline basis for subsequent quality control analysis, clinical review, and medical record archiving. Attached Figure Description
[0017] The invention will now be further described with reference to the accompanying drawings.
[0018] Figure 1 This is a flowchart of the workflow of a two-way data exchange method for pre-hospital and in-hospital emergency care based on wristband identification, as described in this invention. Figure 2 This is a flowchart of the creation and data packet transmission of electronic medical records for pre-hospital emergency care; Figure 3 This is a flowchart of the pre-hospital and in-hospital data linkage and automatic creation of emergency medical records. Detailed Implementation
[0019] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.
[0020] See Figure 1 This invention provides a method for bidirectional data exchange between pre-hospital and in-hospital emergency care based on wristband identification, the specific method including: A disposable passive identification wristband, selected by emergency personnel based on the patient's initial injury level, is acquired. The wristband has a globally unique QR code pre-printed on its surface, with the wristband color corresponding to a specific injury level. In pre-hospital emergency scenarios, the QR code is scanned using an emergency mobile terminal to obtain the wristband code. Basic patient information, physiological parameters, preliminary diagnosis, and implemented emergency measures collected on-site are entered into the emergency electronic medical record. This record is then bound to the wristband code, generating a bound pre-hospital emergency data package. In in-hospital emergency triage scenarios, the QR code is scanned using an emergency triage terminal to read the wristband code. Based on this code, a query request is automatically initiated to the pre-hospital data platform, retrieving and displaying the bound pre-hospital emergency data package in real time. In in-hospital treatment scenarios, the hospital information system uses the wristband code as a global primary key, automatically associating and storing all in-hospital medical records with this code. In the context of patient outcome, the hospital information system automatically extracts key diagnosis and treatment summaries and outcome information. Through a standardized data exchange interface, it proactively pushes the in-hospital treatment data package containing the outcome information back to the emergency center data platform, where it is archived and integrated with the pre-hospital emergency data package to form a complete patient treatment record.
[0021] Example 1: In practice, emergency personnel conduct a rapid on-site assessment of the patient according to a pre-set triage system. This system categorizes patients into four levels: critical, severe, mild, and fatal. Based on the assessment results, emergency personnel select a disposable passive identification wristband of the corresponding color from a color-coded wristband storage unit. The color coding follows internationally accepted standards, with red corresponding to critical level, yellow to severe level, green to mild level, and black to fatal level. The emergency personnel then securely attach the selected disposable passive identification wristband to the patient's wrist, thus physically binding the patient's identity to their injury level.
[0022] Example 2: In specific implementation, refer to Figure 2The emergency mobile terminal initiates its scanning function. The emergency mobile terminal captures an image of the QR code on the surface of the disposable passive identification wristband. The emergency mobile terminal decodes the captured QR code image and extracts a unique wristband code string. The wristband code is displayed in the user interface of the emergency mobile terminal. The emergency mobile terminal automatically creates a blank emergency electronic medical record template indexed by the wristband code. Emergency personnel enter or acquire, through the device, the patient's basic information, continuous physiological parameter waveforms and values, preliminary injury diagnosis text description, and executed emergency measures in the form fields corresponding to the blank emergency electronic medical record template. When the emergency personnel confirm the completion of the data entry and submit it, the emergency mobile terminal logically associates all the entered data with the wristband code, encapsulating it into a structured data packet, namely the bound pre-hospital emergency data packet. The emergency mobile terminal uploads the bound pre-hospital emergency data packet to a designated storage area of the pre-hospital emergency data center in real time via a wireless network, with the wristband code as the primary index key.
[0023] After generating the bound pre-hospital emergency data packet, the emergency mobile terminal calculates the real-time transmission reliability index of the current link through its built-in network quality assessment module. The real-time transmission reliability index The calculation formula is:
[0024] in: This is the current wireless signal strength indicator value, in dBm. The value is obtained in real time by the wireless communication module of the emergency mobile terminal, and the value range is usually from -100dBm to -30dBm; The preset ambient background noise threshold, in dBm. The value is preset by the system administrator based on the typical wireless ambient noise level of the area where the emergency mobile terminal is deployed. The set value is taken from the statistical average of multiple measurements in that area, and the unit is dBm. This represents the currently available uplink bandwidth, in kbps. The value is obtained in real time by the network status monitoring module of the emergency mobile terminal, and the range of the value depends on the current network type and signal quality. The estimated bandwidth required for the transmission of the pre-hospital emergency data packets is expressed in kbps. The value of is calculated by the emergency mobile terminal after encapsulating the pre-hospital emergency data packet, based on the total number of bytes in the data packet and the preset maximum transmission delay requirement. The calculation formula is as follows: ,in The total number of bytes in the data packet. This is the preset maximum transmission delay, in seconds.
[0025] If and only if At that time, the emergency mobile terminal immediately initiates the upload operation of the pre-hospital emergency data packet. If The emergency mobile terminal will temporarily store the pre-hospital emergency data packet in a local encrypted cache and continuously monitor the network status until... Automatic resume transmission after recovery. Specifically, considering the diversity of out-of-hospital emergency scenarios and significant differences in environmental noise levels, the system administrator pre-sets remote configuration updates. Before deploying the emergency mobile terminal, the system administrator uses dedicated drive-testing equipment to continuously measure the wireless environmental noise level in various typical emergency scenarios, such as city centers, residential areas, highways, and remote mountainous areas. The arithmetic mean of multiple measurements for each scenario is used as the reference value for that scenario. A "scenario-noise threshold" mapping table is pre-established on the emergency center data platform's management end, containing different scenario identifiers and their corresponding values. When the emergency mobile terminal is first activated or switches task areas, it obtains its current geographical location information through its built-in GPS module and automatically reports it to the emergency center data platform. The emergency center data platform matches the scenario type based on the location information reported by the terminal, sends the corresponding preset value to the emergency mobile terminal, and automatically writes it into the network quality assessment module as the noise threshold parameter for the current environment. If the terminal is offline and cannot obtain the sent value, it continues to use the value successfully obtained and cached locally last time.
[0026] Example 3: In practice, when a patient arrives at the hospital's emergency triage desk, medical staff use the scanner on the emergency triage terminal to scan the QR code on the patient's wristband. (See also...) Figure 3 The decoding module of the emergency triage terminal decodes the QR code to obtain the wristband code. The communication module of the emergency triage terminal automatically constructs a standardized query request message containing the wristband code and sends it via the hospital intranet to the pre-hospital-in-hospital data interface server deployed at the hospital information boundary. The pre-hospital-in-hospital data interface server receives the standardized query request message, parses the wristband code, and uses the wristband code as an index to initiate a data retrieval in the storage area of the pre-hospital emergency data center. The pre-hospital emergency data center returns a bound pre-hospital emergency data packet matching the wristband code. The pre-hospital-in-hospital data interface server forwards the received bound pre-hospital emergency data packet back to the emergency triage terminal. The display interface of the emergency triage terminal parses and renders the key information in the bound pre-hospital emergency data packet for visualization, and automatically triggers the creation or association of an emergency medical record identified by the wristband code in the hospital information system within the hospital.
[0027] Example 4: In specific implementation, all medical records include examination results, treatment records, medication information, and nursing records. The hospital information system, in its database, establishes a medical context with the wristband code as the core index for the current visit confirmed through the emergency triage process. After successfully acquiring pre-hospital data, the emergency triage terminal sends a patient registration request to the patient management service of the hospital information system. The request carries the wristband code, basic patient information, and visit time. Upon receiving the request, the patient management service of the hospital information system first queries the entire system to see if there is an active medical record with the wristband code as the primary index. If not, a new medical record is created for the patient, and the wristband code is written into the primary index field of the medical record. Simultaneously, the record status is marked as "Emergency Visit in Progress," thus establishing the medical context. If an active record already exists, the new medical activity is associated with the existing medical context to maintain data continuity. When a doctor issues a medical order at the doctor's workstation, the medical order processing module of the hospital information system automatically associates the medical order record with the wristband code in the current medical context. When a nurse performs a nursing procedure and records it through the nurse's workstation, the nursing record module of the hospital information system automatically associates the nursing record with the wristband code. When the laboratory information system or the image archiving and communication system generates a patient's laboratory report or image report, the system uses an inter-system interface to associate the report's unique identifier with the medical record corresponding to the wristband code in the hospital information system. All association operations are automatically completed by the system backend, and the generated structured or unstructured medical data are stored in the hospital's clinical data warehouse with the wristband code as the key index field.
[0028] Example 5: In specific implementation, when a patient's treatment status in the hospital information system changes to "discharged" or "transferred," a data feedback process is triggered. The data extraction module of the hospital information system automatically extracts key information from all medical records associated with the wristband code according to preset summarization rules. This key information includes the final diagnosis, major surgical procedures, important positive test results, discharge medication recommendations, and patient outcome. The summarization rules define the data fields to be extracted, the data source table, and the extraction logic for free text. For structured data fields, the data extraction module directly queries the records associated with the wristband code from a specified table in the database and extracts the values of the specified fields. For unstructured text data, the data extraction module calls a natural language processing engine to parse the medical records and surgical records, identify and extract entities and events that conform to the summarization rules. Entities include disease names, surgical names, and drug names; events include treatment actions and examination findings. The data extraction module fills in all extracted structured field values and entity and event information parsed from the text according to a standardized data format template.
[0029] The data extraction module encapsulates the extracted key information according to the standardized data format defined by the emergency center data platform, generating a structured in-hospital treatment data package. The hospital information system's interface service module pushes the in-hospital treatment data package to the designated data receiving endpoint of the emergency center data platform by calling a pre-configured application programming interface (API). The standardized data exchange interface is implemented using an API based on the Health Level 7 Rapid Medical Interoperability Resource Standard, defining the resource types, data elements, and exchange protocols for pre-hospital emergency data packages and in-hospital treatment data packages. Upon receiving the in-hospital treatment data package, the emergency center data platform's data processing service parses the wristband code and uses it as the key to retrieve and match the corresponding pre-hospital emergency data package.
[0030] The in-hospital treatment data package and the pre-hospital emergency care data package are merged and logically associated in chronological order. The data processing service of the emergency center data platform extracts key event sequences marked with absolute timestamps from both the pre-hospital emergency care data package and the in-hospital treatment data package. A time calibration offset is defined. The calculation formula is:
[0031] in: This refers to the number of the same type of events shared by pre-hospital and in-hospital patients. The value is obtained by the data processing service matching the event types that occur simultaneously in the pre-hospital emergency data package and the in-hospital treatment data package. It is an integer greater than or equal to 1; The first recorded by the hospital's internal system The time of occurrence of a common event, in seconds. The value is provided by the corresponding timestamp extracted from the in-hospital treatment data packet; The first recorded by the pre-hospital system The time of occurrence of the same common event, in seconds. The value is provided by the corresponding timestamp extracted from the pre-hospital emergency data packet.
[0032] The data processing service adds all timestamps to the pre-hospital emergency data packets. A unified calibration is performed, and then the calibrated pre-hospital data packets and in-hospital treatment data packets are merged in chronological order to form a continuous timeline full-process treatment archive with the wristband code as the global identifier. This archive is stored in a unified patient record database, forming a full-process patient treatment archive spanning both pre-hospital and in-hospital stages. The physical meaning of the time calibration offset calculation formula lies in systematically estimating and correcting the fixed deviation between two independent clock sources by calculating the arithmetic mean of the time differences between the pre-hospital and in-hospital systems at multiple recording points of the same treatment event. Pre-hospital emergency mobile terminals and in-hospital hospital information systems typically belong to different network domains and have their own clock sources; before calibration, their timestamps exhibit a relatively stable system-level difference. Selecting objectively occurring, common events of the same type from both records, such as the time points of deterministic operations like "successful first ECG monitoring connection" or "complete establishment of intravenous access," the in-hospital recording time is subtracted from the pre-hospital recording time. The difference for a single event reflects the clock deviation at the time of recording that event. By taking the arithmetic mean of the deviations of such common events, random operational or recording delays that may exist in individual event records can be eliminated, thus obtaining an optimal estimate representing the overall clock deviation between the two systems. By uniformly adding this offset to all timestamps of the pre-hospital data packets, the timeline of pre-hospital events can be logically shifted to align with the in-hospital system clock, ensuring the causal consistency of the merged end-to-end archives in terms of time relationships.
[0033] The foregoing has provided a detailed description of one embodiment of the present invention, but this description is merely a preferred embodiment and should not be construed as limiting the scope of the invention. All equivalent variations and modifications made within the scope of the claims of this invention should still fall within the patent coverage of this invention.
Claims
1. A method for two-way data exchange between pre-hospital and in-hospital emergency care based on wristband identification, characterized in that, include: Obtain a disposable passive identification wristband selected by emergency personnel based on the patient's initial injury level. The disposable passive identification wristband has a globally unique QR code pre-printed on its surface, and the wristband color corresponds to a specific injury level. In pre-hospital emergency scenarios, the patient's basic information, physiological parameters, preliminary diagnosis, and implemented emergency measures collected on-site are scanned by the emergency mobile terminal to obtain the wristband code. The emergency electronic medical record is then entered into the emergency electronic medical record and bound to the wristband code to generate a bound pre-hospital emergency data package. In the hospital emergency triage scenario, the QR code is scanned by the emergency triage terminal, the wristband code is read, and a query request is automatically initiated to the pre-hospital data platform based on the wristband code to obtain and display the bound pre-hospital emergency data package in real time. In hospital treatment scenarios, the hospital information system uses the wristband code as a global primary key to automatically associate and store all medical records generated within the hospital with the wristband code; In the patient outcome scenario, the hospital information system automatically extracts key diagnosis and treatment summaries and outcome information, and actively pushes the in-hospital treatment data package containing the outcome information back to the emergency center data platform through a standardized data exchange interface. It is then archived and integrated with the pre-hospital emergency data package to form a complete patient treatment record. The built-in network quality assessment module calculates the real-time transmission reliability index of the current link. The real-time transmission reliability index The calculation formula is: ; in, This is the current wireless signal strength indicator value, in dBm. This is the preset ambient background noise threshold, in dBm. This represents the currently available uplink bandwidth, in kbps. The estimated bandwidth required for the transmission of the pre-hospital emergency data packet, in kbps; if and only if At that time, the emergency mobile terminal immediately initiates the upload operation of the pre-hospital emergency data packet; if The emergency mobile terminal will temporarily store the pre-hospital emergency data packet in a local encrypted cache and continuously monitor the network status until... Automatic resume download after recovery; The data processing service of the emergency center data platform extracts key event sequences marked with absolute timestamps from pre-hospital emergency data packets and in-hospital treatment data packets; time calibration offset. The calculation formula is: ; in, The number of the same type of events shared by pre-hospital and in-hospital patients; The first recorded by the hospital's internal system The time of occurrence of a common event, in seconds; The first recorded by the pre-hospital system The timestamps of the same common event are displayed in seconds; the data processing service adds all timestamps in the pre-hospital emergency data packet to... A unified calibration is performed, and then the calibrated pre-hospital data package and in-hospital treatment data package are merged in chronological order to form a continuous timeline full-process treatment record with the wristband code as the global identifier.
2. The method for bidirectional data exchange between pre-hospital and in-hospital emergency care based on wristband identification as described in claim 1, characterized in that, The acquisition of a disposable passive identification wristband selected by emergency personnel based on the patient's initial injury level includes: Emergency personnel conduct a rapid on-site assessment of the patient based on a pre-set triage system, which classifies patients into four levels: critical, severe, mild, and fatal. Based on the assessment results, a disposable passive identification wristband of the corresponding color is selected from the wristband storage unit with the corresponding color code. The color code follows the international standard, where red corresponds to the critical level, yellow corresponds to the severe level, green corresponds to the mild level, and black corresponds to the death level. The selected disposable passive identification wristband is securely worn on the patient's wrist to complete the physical identification binding of the patient's identity and injury level.
3. The method for bidirectional data exchange between pre-hospital and in-hospital emergency care based on wristband identification as described in claim 1, characterized in that, The generated pre-hospital emergency data package includes: The scanning function of the emergency mobile terminal is activated to capture an image of the QR code on the surface of the disposable passive identification wristband; The captured QR code image is decoded to extract the unique wristband code string; The wristband code is displayed in the user interface of the emergency mobile terminal, and a blank emergency electronic medical record template indexed by the wristband code is automatically created. Emergency responders enter or acquire the patient's basic information, continuous physiological parameter waveforms and values, preliminary injury diagnosis text description, and executed emergency measures in the form fields corresponding to the blank emergency electronic medical record template. When the emergency personnel confirm that the data entry is complete and submit it, the emergency mobile terminal will logically associate all the data entered with the wristband code and encapsulate it into a structured data packet, namely the bound pre-hospital emergency data packet. The bound pre-hospital emergency data package is uploaded in real time to a designated storage area of the pre-hospital emergency data center via a wireless network, with the wristband code serving as the primary index key for the designated storage area.
4. The method for bidirectional data exchange between pre-hospital and in-hospital emergency care based on wristband identification as described in claim 1, characterized in that, In the in-hospital emergency triage scenario, the emergency triage terminal scans the QR code, reads the wristband code, and automatically initiates a query request to the pre-hospital data platform based on the wristband code. This allows for the real-time acquisition and display of the bound pre-hospital emergency data package, including: When a patient arrives at the hospital's emergency triage desk, medical staff use the scanner on the emergency triage terminal to scan the QR code on the patient's wristband. The decoding module of the emergency triage terminal decodes the QR code to obtain the wristband code; The communication module of the emergency triage terminal automatically constructs a standardized query request message containing the wristband code and sends it to the pre-hospital-in-hospital data interface server deployed at the hospital information boundary through the hospital intranet. The pre-hospital-in-hospital data interface server receives the standardized query request message, parses out the wristband code, and uses the code as an index to initiate a data retrieval in the storage area of the pre-hospital emergency data center; The pre-hospital emergency data center returns a bound pre-hospital emergency data packet that matches the wristband code; The pre-hospital-in-hospital data interface server forwards the received pre-hospital emergency data packets back to the emergency triage terminal. The display interface of the emergency triage terminal parses and renders the key information in the bound pre-hospital emergency data package, displays it visually, and automatically triggers the creation or association of an emergency medical record identified by the wristband code in the hospital information system.
5. A method for bidirectional data exchange between pre-hospital and in-hospital emergency care based on wristband identification, as described in claim 1, is characterized in that... In the in-hospital treatment scenario, the hospital information system uses the wristband code as the global primary key to automatically associate and store all medical records generated within the hospital with the wristband code, including: All medical records include examination results, treatment records, medication information, and nursing records; The hospital information system establishes a visit context in its database for the visit event confirmed through the emergency triage process, with the wristband code as the core index. When a doctor issues a medical order at the doctor's workstation, the medical order processing module of the hospital information system automatically associates the medical order record with the wristband code in the current medical context; When a nurse performs a nursing procedure and records it at the nurse's workstation, the nursing record module of the hospital information system automatically associates the nursing record with the wristband code; When the laboratory information system or the image archiving and communication system generates a patient's laboratory report or image report, the unique identifier of the report is associated with the medical record corresponding to the wristband code in the hospital information system through the inter-system interface call; All related operations are completed automatically by the system backend, and the generated structured or unstructured medical data are stored in the hospital's clinical data warehouse with the wristband code as the key index field.
6. A method for bidirectional data exchange between pre-hospital and in-hospital emergency care based on wristband identification, as described in claim 5, is characterized in that... The hospital information system, in its database, establishes a visit context with the wristband code as the core index for the current visit event confirmed through the emergency triage process, including: After successfully acquiring pre-hospital data, the emergency triage terminal sends a patient registration request to the patient management service of the hospital information system. The request carries the wristband code, basic patient information, and consultation time. After receiving the request, the patient management service of the hospital information system first queries the entire system to see if there are any active medical records indexed by the wristband code. If it does not exist, a new medical record is created for the patient, and the wristband code is written into the main index field of the medical record. At the same time, the status of the record is marked as "Emergency Treatment in Progress", thereby establishing the medical context. If an active record already exists, the new treatment activity will be associated with the existing treatment context to ensure data continuity.
7. A method for bidirectional data exchange between pre-hospital and in-hospital emergency care based on wristband identification, as described in claim 1, is characterized in that... The formation of a complete patient treatment record includes: When a patient's medical status in the hospital information system changes to "discharged" or "transferred", the data feedback process is triggered. The data extraction module of the hospital information system automatically extracts key information from all medical records associated with the wristband code according to preset summary rules. The key information includes final diagnosis, major surgical procedures, important positive test results, discharge medication recommendations, and treatment outcomes. The data extraction module encapsulates the extracted key information according to the standardized data format defined by the emergency center data platform to generate a structured in-hospital treatment data package. The interface service module of the hospital information system pushes the in-hospital treatment data package to the data receiving endpoint designated by the emergency center data platform by calling the pre-configured application programming interface. After receiving the in-hospital emergency care data packet, the data processing service of the emergency center data platform parses out the wristband code in it, and uses the code as the key to retrieve and match the corresponding pre-hospital emergency care data packet; The in-hospital treatment data package and the pre-hospital emergency data package are merged and logically linked in chronological order and stored in a unified patient file database to form a complete patient treatment file spanning both pre-hospital and in-hospital stages.
8. A method for bidirectional data exchange between pre-hospital and in-hospital emergency care based on wristband identification, as described in claim 7, is characterized in that... The data extraction module of the hospital information system automatically extracts key information from all medical records associated with the wristband code according to preset summary rules, including: The summary rules define the data fields to be extracted, the data source table, and the extraction logic for free text; For structured data fields, the data extraction module directly queries the records associated with the wristband code from a specified table in the database and extracts the values of the specified fields. For unstructured text data, the data extraction module calls a natural language processing engine to parse the medical record and surgical record text, identify and extract entities and events that conform to the summary rules. The entities include disease names, surgical names, and drug names, and the events include treatment behaviors and examination findings. All extracted structured field values and entity and event information parsed from the text are populated according to a standardized data format template.
9. A method for bidirectional data exchange between pre-hospital and in-hospital emergency care based on wristband identification, as described in claim 1, is characterized in that... The standardized data exchange interface is implemented using an application programming interface based on the Health Level 7 Rapid Medical Interoperability Resource Standard. The standardized data exchange interface defines the resource types, data elements, and exchange protocols of pre-hospital emergency data packets and in-hospital treatment data packets.
10. A two-way data communication system for pre-hospital and in-hospital emergency care based on wristband identification, comprising a memory, a processor, and a computer program stored in the memory and running on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method for bidirectional data exchange between pre-hospital and in-hospital emergency care based on wristband identification as described in any one of claims 1 to 9.
Citation Information
Patent Citations
Portable multifunctional integrated transfer platform for pre-hospital first aid
CN122000002A
Hospital uses information identification wrist strap
CN205624807U