Treatment scheme data distribution method, computer device and storage medium

Abstract

The invention relates to the technical field of medical data processing, and provides a data distribution method of a treatment scheme, a computer device and a storage medium, and the method comprises the steps: a server side responds to a confirmation operation of a user on scheme data of the treatment scheme, stores the scheme data, and screens a to-be-selected treatment equipment set suitable for the treatment scheme from all treatment equipment; distributing the scheme data to each target treatment device selected from the to-be-selected treatment device set; the server side establishes a mapping relation between the treatment scheme and one or more target treatment devices; the mapping relation is used for determining a synchronization object when the scheme data of the treatment scheme is modified. Therefore, according to the treatment scheme, the applicable treatment equipment is screened, distribution of the scheme data to batch equipment is automatically completed, a synchronization mechanism during modification is provided, the problems in the related technology are effectively solved, the distribution efficiency of the treatment scheme is improved, errors are reduced, and efficient synchronization during scheme modification is achieved.

Description

Technical Field

[0001] This disclosure relates to the field of medical data processing technology, and in particular to a data distribution method, computer device, and storage medium for treatment plans. Background Technology

[0002] In rehabilitation therapy equipment systems, therapists often need to create customized rehabilitation training programs that can be used on multiple rehabilitation training devices to provide standardized rehabilitation training services for different patients. However, in related technologies, the distribution and management mechanisms for rehabilitation training programs to various devices lack automated mechanisms, leading to inefficiency and a high risk of errors.

[0003] Specifically, on the one hand, when a therapist creates a rehabilitation training program on a certain device, the program cannot be automatically distributed to other similar devices. The therapist needs to manually configure it on each device, which is inefficient and prone to errors.

[0004] On the other hand, when treatment plan data is shared among multiple rehabilitation training devices, if one rehabilitation training device modifies or deletes the plan, other rehabilitation training devices will not be able to know the modification in time. This will lead to inconsistencies in the plan data on different rehabilitation training devices, causing conflicts and affecting the treatment effect when the user changes rehabilitation training devices for treatment. Summary of the Invention

[0005] In view of the shortcomings of the prior art described above, the purpose of this disclosure is to provide a data distribution method, computer device and storage medium for treatment plans, and to solve the problems in the related art.

[0006] The first aspect of this disclosure provides a data distribution method for a treatment plan, comprising: a server-side responding to a user's confirmation operation on the plan data of a treatment plan, storing the plan data, and providing a set of candidate treatment devices applicable to the treatment plan; the server-side responding to a user selecting one or more target treatment devices from the set of candidate treatment devices, distributing the plan data to each of the target treatment devices; the server-side establishing a mapping relationship between the treatment plan and the one or more target treatment devices; the mapping relationship being used to determine the synchronization object when the plan data of the treatment plan is modified.

[0007] In an embodiment of the first aspect, the server, in response to a user's confirmation operation of the treatment plan data, stores the treatment plan data and provides a set of candidate treatment devices applicable to the treatment plan, including: in response to a user initiating a creation / editing request for the treatment plan to the server, providing a graphical interface for creating / editing the treatment plan data; and in response to the user's confirmation of the treatment plan data, displaying the set of applicable candidate treatment devices associated with the treatment plan.

[0008] In the first aspect of the embodiment, the method for determining the applicable device type of the treatment plan includes at least one of the following: 1) determining the device type based on the user's selection of the device type when creating the treatment plan on the server side; 2) receiving the plan data of the treatment plan created and sent by the treatment device, querying the device type to which the treatment device belongs based on the device identifier of the treatment device extracted from the plan data, and using it as the applicable device type of the treatment plan.

[0009] In an embodiment of the first aspect, the server-side establishes a mapping relationship between the treatment plan and the one or more target treatment devices, including: the server-side assigns a first plan identifier to the treatment plan and establishes a mapping relationship between the first plan identifier and the device identifier of each target treatment device; the first plan identifier is used to distribute to each target treatment device along with the plan data; the server-side obtains the returned first plan identifier and second plan identifier from each target treatment device to which the plan data is distributed; wherein the second plan identifier is assigned by the target treatment device to the treatment plan; and the server-side establishes a mapping relationship between the first plan identifier and the second plan identifier of each target treatment device.

[0010] In an embodiment of the first aspect, the data distribution method for the treatment plan further includes: the server acquiring plan modification information of the treatment plan, the plan modification information including modified plan data and a first plan identifier or a second plan identifier; the plan data carrying a device identifier of the treatment device; the server acquiring the first identifier, or determining the first identifier based on the second identifier and the device identifier in the plan data through the mapping relationship, and querying the device identifier of each treatment device associated with the first plan identifier based on the first identifier in the mapping relationship; the server synchronizing the modified plan data to the treatment device corresponding to the queried device identifier to update the plan data of the treatment plan on the treatment device.

[0011] In an embodiment of the first aspect, the server-side acquisition of treatment plan modification data includes at least one of the following: 1) the server-side acquisition of a user-initiated plan modification request, the modification request including modified plan data and a first plan identifier; 2) the server-side receiving a plan modification data packet from the current treatment device, the plan modification data packet including modified plan data and a second plan identifier; wherein the current treatment device is excluded from the synchronized treatment devices.

[0012] In an embodiment of the first aspect, before distributing the scheme data to each of the target treatment devices, the method further includes: the server acquiring device configuration information for each of the target treatment devices; the server adjusting the scheme data to be compatible with the device configuration information in response to detecting a conflict between the device configuration information of the target treatment device and the scheme data; and the server distributing the adjusted scheme data to the corresponding target treatment device.

[0013] In an embodiment of the first aspect, the data distribution method for the treatment plan further includes: the server receiving plan data sent by the treatment device when creating or modifying the treatment plan; the treatment device comparing multiple plan data belonging to the same treatment plan to determine whether there is a conflict; in response to the existence of a conflict, the server identifying the conflict type based on the conflicting data items and / or the device to which the conflicting plan data belongs among the multiple plan data of the same treatment plan; and the server determining an applicable conflict resolution strategy based on the identified conflict type, and resolving the conflict through the conflict resolution strategy.

[0014] In an embodiment of the first aspect, the scheme data includes basic scheme information, scheme task information, and timestamps; the conflict resolution strategy includes at least one of the following: a timestamp priority strategy, a server-side priority strategy, and a merging strategy; the timestamp priority strategy is applicable to a first conflict type where multiple treatment devices modify the basic scheme information, and is implemented to retain the scheme data with the newest timestamp among the scheme data involved in the conflict; the server-side priority strategy is applicable to a second conflict type where there is a conflict between scheme data created on the server and scheme data provided by the treatment devices, and is implemented to prioritize retaining the scheme data created on the server; the merging strategy is applicable to a third conflict type where multiple treatment devices modify the scheme task information, and updates the modified content of each treatment device to the scheme data according to the timestamp order.

[0015] In an embodiment of the first aspect, the protocol data includes a plan template version number so that it can be extracted by the server, and the device configuration information includes a plan template for selecting protocol task information; or, the server obtains the device configuration information by communicating with the target treatment device or from locally stored data.

[0016] In an embodiment of the first aspect, the step of adjusting the plan data to be compatible with the device configuration information in response to detecting a conflict between the device configuration information of the target treatment device and the plan data includes at least one of the following: 1) In response to detecting a conflict between the device configuration information of the target treatment device and the task execution parameter value of the plan task information in the plan data, modifying the task execution parameter value to adapt to the device configuration information; 2) In response to detecting a partial functional difference between the target treatment device and the treatment device that is the source of the plan data, disabling or deleting task items corresponding to the partial functions in the plan task information of the plan data.

[0017] In an embodiment of the first aspect, the data distribution method for the treatment plan further includes: the treatment device displaying available plan data; in response to a user's application operation on the plan data, the treatment device generating a medical task based on the operated plan data for execution.

[0018] In an embodiment of the first aspect, before the treatment device displays available protocol data, the method further includes: obtaining a patient identifier of a patient using the treatment device; querying the patient's physical condition data based on the patient identifier; and querying protocol data having task execution parameter values ​​that match the physical condition data; wherein the matching indicates that the patient's physical condition represented by the physical condition data matches the medical intensity represented by the task execution parameter values.

[0019] In the embodiments of the first aspect, at least one of the following is also included: 1) recording the distribution status of the protocol data for each treatment plan; 2) detecting treatment devices with a failed distribution status and performing a distribution retry; 3) periodically verifying the consistency of the protocol data of the treatment plan on the server and the treatment device, and triggering resynchronization when there is inconsistency.

[0020] A second aspect of this disclosure provides a computer apparatus, comprising: a processor and a memory; the memory storing a computer program or instructions; the processor being configured to run the computer program or instructions to perform a data distribution method for a treatment protocol as described in any one aspect of the first disclosure.

[0021] A third aspect of this disclosure provides a computer-readable storage medium storing a computer program or instructions, which, when executed, perform a data distribution method for a treatment regimen as described in any one of the first aspects.

[0022] As described above, this disclosure relates to the field of medical data processing technology, providing a data distribution method, computer device, and storage medium for treatment plans. The method includes: a server-side responding to a user's confirmation operation on the treatment plan data, storing the plan data, and providing a set of candidate treatment devices applicable to the treatment plan; the server-side responding to a user selecting one or more target treatment devices from the set of candidate treatment devices, distributing the plan data to each of the target treatment devices; the server-side establishing a mapping relationship between the treatment plan and the one or more target treatment devices; the mapping relationship being used to determine the synchronization object when the treatment plan data is modified. Therefore, this disclosure achieves the screening of applicable treatment devices based on the treatment plan, automatically completing the distribution of plan data to batch devices, and providing a synchronization mechanism during modifications, effectively solving problems in related technologies, improving the distribution efficiency of treatment plans, reducing errors, and achieving efficient synchronization during plan modifications. Attached Figure Description

[0023] Figure 1 A schematic diagram illustrating an application scenario in one embodiment of this disclosure is shown.

[0024] Figure 2 A flowchart illustrating a data distribution method for a treatment plan according to one embodiment of this disclosure is shown.

[0025] Figure 3 This illustration shows a flowchart of a process in one embodiment of the present disclosure, illustrating how the server establishes a mapping relationship between the treatment plan and one or more target treatment devices.

[0026] Figure 4 This illustration shows a schematic diagram of the interaction process in a specific embodiment of the present disclosure, in which a user terminal creates a treatment plan on the server side and distributes it to multiple treatment devices.

[0027] Figure 5 A flowchart illustrating a data distribution method for a treatment plan in yet another embodiment of this disclosure is shown.

[0028] Figure 6 This document presents a flowchart illustrating the communication interaction process for data synchronization updates in a modified scheme under a first scenario in one embodiment of this disclosure.

[0029] Figure 7 This document presents a flowchart illustrating the communication interaction process for data synchronization updates in the modified scheme under the second scenario of an embodiment of this disclosure.

[0030] Figure 8 This is a flowchart illustrating an embodiment of the present disclosure of a scheme for adjusting the device configuration of a target treatment device to be distributed.

[0031] Figure 9A flowchart illustrating the conflict resolution mechanism in one embodiment of this disclosure is shown.

[0032] Figure 10 A schematic flowchart illustrating the application of a treatment plan using a treatment device is shown in one embodiment of this disclosure.

[0033] Figure 11 A schematic diagram of a data distribution device for a treatment plan is shown in one embodiment of this disclosure.

[0034] Figure 12 A schematic diagram of the structure of a computer device according to an embodiment of the present disclosure is shown. Detailed Implementation

[0035] The following specific examples illustrate the implementation of this disclosure. Those skilled in the art can easily understand other advantages and effects of this disclosure from the information disclosed herein. This disclosure can also be implemented or applied through other different specific embodiments, and various details in this disclosure can be modified or changed according to different viewpoints and application modules without departing from the spirit of this disclosure. It should be noted that, unless otherwise specified, the embodiments and features in the embodiments of this disclosure can be combined with each other.

[0036] The embodiments of this disclosure will now be described in detail with reference to the accompanying drawings, so that those skilled in the art to which this disclosure pertains can readily implement it. This disclosure may be embodied in many different forms and is not limited to the embodiments described herein.

[0037] In this disclosure, references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic represented in connection with that embodiment or example is included in at least one embodiment or example of this disclosure. Furthermore, the specific features, structures, materials, or characteristics represented may be combined in any suitable manner in any one or a group of embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples represented in this disclosure, as well as the features of those different embodiments or examples.

[0038] Furthermore, the terms "first" and "second" are used for illustrative purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the representation of this disclosure, "a set" means two or more, unless otherwise explicitly specified.

[0039] For the purpose of clarity, devices unrelated to the description are omitted, and the same or similar components throughout the specification are given the same reference numerals.

[0040] Throughout this specification, when it is said that a device is "connected" to another device, this includes not only "direct connection" but also "indirect connection" by placing other components in between. Furthermore, when it is said that a device "comprises" a certain constituent element, unless otherwise stated otherwise, this does not exclude other constituent elements, but rather implies that other constituent elements may be included.

[0041] While the terms first, second, etc., are used in some examples herein to refer to various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, first interface and second interface, etc., are used. Furthermore, as used herein, the singular forms “a,” “an,” and “the” are intended to also include the plural forms unless the context indicates otherwise. It should be further understood that the terms “comprising,” “including,” indicate the presence of the stated feature, step, operation, element, module, item, kind, and / or group, but do not exclude the presence, occurrence, or addition of one or more other features, steps, operations, elements, modules, items, kinds, and / or groups. The terms “or” and “and / or” as used herein are interpreted as inclusive, or mean any one or any combination thereof. Thus, “A, B, or C” or “A, B, and / or C” means “any one of: A; B; C; A and B; A and C; B and C; A, B, and C.” Exceptions to this definition will only occur if the combination of elements, functions, steps, or operations is inherently mutually exclusive in some way.

[0042] The technical terms used herein are for reference only to specific embodiments and are not intended to limit the scope of this disclosure. The singular form used herein includes the plural form unless the statement explicitly indicates otherwise. The word "comprising" as used in this specification means to specify a particular characteristic, region, integer, step, operation, element, and / or component, and does not exclude the presence or addition of other characteristics, regions, integers, steps, operations, elements, and / or components.

[0043] Although not explicitly defined, all terms, including technical and scientific terms used herein, shall have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. Terms defined in commonly used dictionaries shall be further interpreted as having a meaning consistent with the relevant technical literature and the message of the present disclosure, and shall not be over-interpreted as having an ideal or overly formulaic meaning unless otherwise defined.

[0044] In rehabilitation therapy equipment systems, therapists often need to create customized rehabilitation training programs that can be used on multiple rehabilitation training devices to provide standardized rehabilitation training services for different patients. However, in related technologies, the distribution and management mechanisms for rehabilitation training programs to various devices lack automated mechanisms, leading to inefficiency and a high risk of errors.

[0045] Specifically, when a therapist creates a rehabilitation training plan on one device, the plan cannot be automatically distributed to other similar devices. The therapist must manually configure it on each device, which is inefficient and prone to errors. Furthermore, when plan data is shared across multiple rehabilitation training devices, if one device modifies or deletes the plan, other devices may not be aware of the change in time. This can lead to inconsistencies and conflicts in the plan data across different devices, negatively impacting the treatment effectiveness when the user switches to a different device.

[0046] In view of this, the data distribution method for treatment plans provided in this disclosure embodiment can realize the automated batch distribution and data synchronization of treatment plan data, thereby solving the problems in related technologies.

[0047] like Figure 1 The diagram shown illustrates an application scenario in one embodiment of this disclosure.

[0048] exist Figure 1 The image illustrates a communication system architecture for medical network communication. The communication system includes a treatment device 101, a server 102, and a user terminal 103.

[0049] The treatment device 101 is communicatively connected to the server 102, and the server 102 is communicatively connected to the user terminal 103. In some embodiments, the treatment device 101, server 102, and user terminal 103 are all located in a secure and trusted local network. The server 102 is a server / server group set up locally in the medical institution. The user terminal 103 is a terminal with a wired / wireless connection between the medical institution and the local server. The treatment device 101 is a device set up locally in the medical institution for treating patients. Thus, the treatment device 101, server 102, and user terminal 103 communicate using a secure and trusted local network to ensure data security in medical scenarios. In some other embodiments, the treatment device 101 and server 102 form a communication connection in a secure and trusted local network, and the user terminal 103 can access the server 102 in the local network with preset permissions through an external network. In still some embodiments, the treatment device 101 is located in a secure and trusted local network, and the server 102 and user terminal 103 are located in an external network. The user terminal 103 accesses the server 102 via an external network with authorized access. The server 102 connects to the local network via an external network with authorized access to the local network and communicates with the treatment device 101. The user terminal 103 communicates with the server 102. In some embodiments, there may be multiple servers 102, located on both the local network and the external network and communicating with each other. The server 102 on the local network can communicate with the local user terminal 103 and the treatment device 101 via the local network, while the server 102 on the external network can connect to external user terminals 103 via the external network.

[0050] In some embodiments, the local network may include a local area network (LAN) of a medical institution (such as a hospital, clinic, etc.). In some embodiments, the external network may include a wide area network (WAN), or a hybrid network of WAN and LAN. For example, the WAN may include at least one of the Internet and a mobile operator's 4G / 5G mobile Internet.

[0051] In some embodiments, the wide area network or local area network can be a network formed based on wired communication connections, wireless communication connections, or a combination of wired and wireless communication connections. Wired communication connections include those formed via wired media such as optical fibers or network cables. Wireless communication connections include those formed via radio frequency signals, such as Bluetooth, WiFi, 4G / 5G, etc.

[0052] Internet of Things (such as Zigbee, Lora, NB-IoT), etc.

[0053] In some embodiments, the treatment device 101 can be implemented as a rehabilitation training device. The rehabilitation training device is used to help patients recover their physical functions. As an example, the rehabilitation training device may include one or more of the following: physical therapy device 101, sports rehabilitation device, speech rehabilitation device, cognitive and vocational rehabilitation device, assistive devices, etc. The physical therapy device 101 includes one or more of the following: electrotherapy device, ultrasound therapy device 101, magnetotherapy device, and hot / cold compress device. The electrotherapy device includes devices such as low-frequency electrotherapy devices and medium-frequency electrotherapy devices, which stimulate muscles with electric current to promote blood circulation and relieve pain. The ultrasound therapy device utilizes the vibration and heating effects of ultrasound waves to promote tissue repair and inflammation absorption. The magnetotherapy device, such as a magnetotherapy device, acts on the human body through a magnetic field to relieve pain and promote blood circulation. The hot / cold compress device uses cold compresses to reduce swelling and pain, while hot compresses help promote blood circulation and muscle relaxation. The sports rehabilitation device includes one or more of the following: limb rehabilitation training devices, such as limb training devices, balance training devices, gait trainers, etc. The speech rehabilitation device includes one or more of the following: speech training devices, pronunciation training devices, swallowing training devices, etc. The language training equipment provides language training tasks and assessment tools to help patients with language disorders improve their pronunciation and expression abilities. Pronunciation training equipment, such as pronunciation correctors, targets specific pronunciation problems. Swallowing training equipment assists patients with swallowing disorders in swallowing function training. Cognitive and vocational rehabilitation equipment includes one or more of the following: cognitive ability training equipment, hand function training equipment, and daily living skills training equipment. Cognitive ability training equipment includes memory training equipment and attention training equipment to improve patients' cognitive function. Hand function training equipment includes hand grip strengtheners and finger dexterity trainers to help restore hand function. Daily living skills training equipment includes simulated kitchen utensils and dressing trainers to help patients regain their ability to perform daily activities independently. Assistive devices include wheelchairs, crutches, orthotics, standing beds, and commode chairs to provide mobility, orthotics, and support for patients with limited mobility. Other rehabilitation equipment includes neuromuscular electrical stimulators, shockwave therapy devices, microwave therapy devices, and shortwave therapy devices. Neuromuscular electrical stimulators are used to promote the recovery of nerve and muscle function through electrical stimulation. The shockwave therapy device utilizes the physical effects of shockwaves to treat diseases of muscles and bones. The microwave therapy device and shortwave therapy device are used to improve local blood circulation and promote the absorption of inflammation.

[0054] In some embodiments, the treatment device 101 integrates a circuit module for intelligent processing and IoT communication capabilities, including components such as a processor, memory, and a communicator. The processor may include MCU, CPU, SoC, or FPGA, and the memory may include RAM or ROM. The communicator includes a wired communication interface and / or a wireless communication interface. The processor can run computer programs stored in the memory to achieve the required functions, such as the operation of the treatment device 101 and its interaction with external systems.

[0055] It should be noted that the types of rehabilitation training equipment listed above are merely examples. In actual scenarios, the types of rehabilitation training equipment can vary and are not limited to those listed above. Furthermore, the integration of multiple rehabilitation training functions into a single rehabilitation training device is also not limited to the types listed above.

[0056] In addition to rehabilitation training equipment, the treatment equipment 101 may also include other equipment with communication and treatment capabilities, which are not listed here and are not limited to rehabilitation training equipment.

[0057] In some embodiments, the server-side 102 may be implemented on a server / server group or other device (such as a desktop computer). The server-side 102 may include server-side programs.

[0058] In some embodiments, the user terminal 103 includes, but is not limited to, a desktop computer or a mobile terminal. The mobile terminal includes one or more of the following: a laptop computer, a smartphone, a tablet computer, a smartwatch, and smart glasses.

[0059] The data distribution method for treatment plans in this embodiment can be applied to... Figure 1 In a communication system. For example, the data distribution method may include steps performed by the server 102. Optionally, it may also include steps performed by the treatment device 101.

[0060] like Figure 2 The diagram shown illustrates a flowchart of a data distribution method for a treatment plan according to an embodiment of this disclosure.

[0061] exist Figure 2 The data distribution method includes:

[0062] Step S201: In response to the user's confirmation of the treatment plan data, the server stores the treatment plan data and provides a set of candidate treatment devices applicable to the treatment plan.

[0063] In some embodiments, users can create treatment plans on the server side, and the set of candidate treatment devices is determined by a confirmation operation on the plan data during the creation process. Further, the server side can respond to the user's selection of device types when creating a treatment plan on the server side. In a specific example, the user can connect to and log in to the server side through a user terminal, and the server side can display a first graphical interface for creating a treatment plan to the user through the user terminal. The first graphical interface can display a set of "device types" (e.g., device type 1, device type 2, device type 3, etc.) for the user to select to determine the device type. For example, different types of rehabilitation training devices, such as upper limb, lower limb, etc. After selecting and confirming the device type, the user can jump to a second graphical interface to add the data required to create the treatment plan. The data required to create the plan can include plan task information. For rehabilitation training devices, the plan task information includes, for example, rehabilitation training tasks for the upper limb. Optionally, each device type can contain multiple task types, which can be displayed on the second graphical interface for selection. After selecting and confirming the plan task information, plan data is formed and stored. Optionally, the second graphical interface for selecting treatment plan task information may provide an option to save the plan, allowing the user to confirm and save it as treatment plan data. In this embodiment, the operation of saving the plan is equivalent to confirming the treatment plan data. Further, the user can be redirected to a third graphical interface for filtering target treatment devices from which the treatment plan data needs to be distributed. In this embodiment, based on a pre-selected device type, the server may display a set of candidate treatment devices matching the selected device type from the connected treatment devices in the third graphical interface.

[0064] In some embodiments, the set of candidate treatment devices belongs to a device type compatible with the treatment plan and consists of available treatment devices. For example, if the treatment plan is upper limb training, then the set of candidate treatment devices includes only treatment devices with upper limb training functions. Furthermore, these devices must be currently functioning normally, not disconnected, and usable for training.

[0065] In some embodiments, the solution data created on the server side may include basic solution information (such as name, solution description, etc.), solution task information (such as task list, etc.), and solution association information. The solution association information may include timestamps, such as the timestamp when the solution data was created / modified and saved.

[0066] In other embodiments, the user can also edit the created treatment plan on the server side, and the set of candidate treatment devices is determined by a confirmation operation on the plan data during the editing process. Further, the server side can respond to the user's selection of device type when editing the treatment plan on the server side. In a specific example, the treatment plan may have been previously created on the server side, or it may have been created / modified and reported from a treatment device. As an example, a fourth graphical interface can be provided for editing an existing treatment plan. During the editing process, the second graphical interface described above can be repeated to confirm the plan task information, i.e., the plan data confirmation operation. Further, a third graphical interface is displayed to show the set of treatment devices that conform to the device type. The difference between this embodiment and the previous embodiment for creating treatment plans is that the set of treatment devices displayed in the third graphical interface includes pre-selected target treatment devices. Optionally, for selected target treatment devices, the user can be allowed to deselect, or the user can be restricted from deselecting. Further optionally, online / offline target treatment devices can be displayed separately; unavailable target treatment devices can be filtered out and not displayed.

[0067] In the above embodiments, the set of treatment devices is determined based on the current or pre-associated device type when creating / editing treatment plan data on the server side. In other embodiments, for treatment plan data created / modified on a treatment device and reported to the server side, the treatment device's device identifier may be carried, which may be implemented as the device's serial number (or model). Then, after receiving the treatment plan data, the server side can extract the device identifier from the treatment plan data, and can query and determine the device information of the treatment device based on the device identifier, and determine the device type corresponding to the device identifier. Thus, the treatment plan data created / modified and sent on the treatment device can be stored on the server side in association with the device type, and the corresponding set of treatment devices can be displayed when the user edits the treatment plan data on the server side. In some embodiments, the server side can perform integrity verification on the treatment plan data received from the treatment device to ensure its integrity.

[0068] Step S202: In response to a user selecting one or more target treatment devices from the set of candidate treatment devices, the server distributes the treatment plan data to each of the target treatment devices.

[0069] Specifically, based on the set of treatment devices displayed in the third graphical interface of the above embodiments, the user can select one or more of the target treatment devices to determine the recipients of the treatment plan.

[0070] In some alternative embodiments, if the target treatment device has multiple device types, the server can group the target treatment devices according to device type and distribute the treatment plan data to each group of devices separately. Optionally, the server can use a message queue or push mechanism to ensure reliable transmission of the treatment plan data.

[0071] Step S203: The server establishes a mapping relationship between the treatment plan and the one or more target treatment devices.

[0072] The server can establish the mapping relationship to determine the synchronization targets when the treatment plan data is modified. Specifically, through the distribution, multiple treatment devices share the same treatment plan data. However, the plan data stored locally on each treatment device and the server can be modified independently, so there may be differences between these plan data. Therefore, when one of the plan data is modified, the plan data needs to be synchronized between the treatment devices sharing the same treatment plan and the server to maintain consistency. Thus, by establishing the mapping relationship, if the treatment plan data is modified, other devices sharing the treatment plan can be queried using the mapping relationship, facilitating the automatic synchronization of the modified plan data.

[0073] like Figure 3 The diagram illustrates a process in one embodiment of this disclosure where the server establishes a mapping relationship between the treatment plan and one or more target treatment devices.

[0074] exist Figure 3 The process includes:

[0075] Step S301: The server assigns a first scheme identifier to the treatment scheme and establishes a mapping relationship between the first scheme identifier and the device identifier of each target treatment device.

[0076] The first scheme identifier is distributed to each of the target treatment devices along with the scheme data. In an optional example, the first scheme identifier may be included in the data structure of the scheme data for extraction. Alternatively, the first scheme identifier may be independent of the scheme data. In some embodiments, the first scheme identifier is a globally unique scheme identifier assigned by the server for each treatment scheme, so that the treatment scheme can be uniquely identified on the server, user terminal, or treatment device.

[0077] By establishing a mapping relationship between the first scheme identifier and the device identifier of the treatment device, when the treatment scheme corresponding to the first scheme identifier is modified, the treatment device that needs to be synchronized can be automatically queried through this mapping relationship.

[0078] Step S302: The server obtains the first scheme identifier and the second scheme identifier from each target treatment device that has received the scheme data.

[0079] The second scheme identifier is assigned to the treatment scheme by the target treatment device. In some embodiments, the second scheme identifier is a scheme identifier that is locally unique to the treatment device, but duplicates may exist across different treatment devices.

[0080] Step S303: The server establishes a mapping relationship between the first scheme identifier and the second scheme identifier of each target treatment device.

[0081] Therefore, by establishing a mapping relationship between the first scheme identifier and the device identifier, and a mapping relationship between the second scheme identifier and the first scheme identifier, a mapping relationship of "first scheme identifier - device identifier - second scheme identifier" is actually established. On the server side, the associated second scheme identifier and device identifier can be uniquely determined based on the first scheme identifier to perform the synchronization of the treatment scheme to the treatment device. Alternatively, the associated first scheme identifier can be uniquely determined based on the second scheme identifier and the device identifier, thereby uniquely determining the treatment scheme.

[0082] like Figure 4 The diagram illustrates the interactive process of a user terminal creating a treatment plan on the server side and distributing it to multiple treatment devices in a specific embodiment of this disclosure.

[0083] In this embodiment, the user terminal, server, and multiple treatment devices are represented as device A, device B, and device C. Device A has device identifier SN001, device B has device identifier SN002, and device C has device identifier SN003.

[0084] Step S401: The user terminal sends a request to the service terminal to create a new treatment plan.

[0085] Referring to the previous embodiments, the user terminal sends the treatment plan data to the service terminal, and selects a list of target treatment devices (SNs) to which the treatment plan needs to be distributed, such as device A, device B, and device C. The SN list includes SN001, SN002, and SN003.

[0086] Optionally, the server can verify the validity of the SNs in the SN list, i.e., whether the corresponding treatment device exists / is available.

[0087] Step S402: The server generates a first treatment plan identifier S001 for the treatment plan.

[0088] Then, the database transaction begins. Optionally, the server adds fields to the database for scheme S001, such as scheme identifier, name, description, etc., corresponding to the scheme's basic information.

[0089] Step S403: The server generates a mapping relationship between the first scheme identifier and the device identifier in the SN list.

[0090] For example, (S001, SN001), (S001, SN002), (S001, SN003).

[0091] Based on the above information, submit the database transaction to store the solution data as structured data in the database.

[0092] Step S404: The server sends the treatment plan along with S001 to devices A, B, and C in parallel according to SN001, SN002, and SN003 respectively.

[0093] Step S405: Device A, Device B and Device C respectively store the scheme data and generate the second scheme identifiers D123, D456 and D789.

[0094] Step S406: Device A, Device B and Device C respectively return a scheme creation confirmation message to the server, carrying their respective second scheme identifiers D123, D456 and D789.

[0095] Step S407: The server records and establishes the mapping relationship between the first scheme identifier S001 and each group of device identifiers of device A, device B, and device C, and the second scheme identifier.

[0096] For example, (S001, SN001, D123), (S001, SN002, D456), (S001, SN003, D789).

[0097] Step S408: The server sends a creation completion notification carrying S001 to the user terminal.

[0098] like Figure 5 The diagram shown illustrates a flowchart of a data distribution method for a treatment plan in yet another embodiment of this disclosure.

[0099] exist Figure 5 The process includes:

[0100] Step S501: The server obtains the treatment plan modification information, which includes the modified plan data and the first plan identifier or the second plan identifier.

[0101] The treatment plan data carries a device identifier for the treatment device. This device identifier originates from the treatment device that created / modified the treatment plan and reported it to the server, as can be found in previous embodiments. In some embodiments, the modified treatment plan data can be full data; alternatively, it can be incremental data.

[0102] In some embodiments, the user terminal initiates a plan modification request to the server; this can be referred to as the first scenario of "server-side plan modification," in which case the plan modification information is included in the plan modification request. In other embodiments, the treatment device may report a plan modification data packet to the server; this can be referred to as the second scenario of "device-side plan modification," in which case the plan modification information is included in the plan modification data packet.

[0103] Step S502: The server obtains the first identifier, or identifies it through the mapping relationship based on the second identifier and the device identifier in the scheme data, and queries the device identifier of each treatment device associated with the first scheme identifier in the mapping relationship based on the first identifier.

[0104] Specifically, based on the pre-established mapping relationship of "first scheme identifier - device identifier - second scheme identifier", the server can determine the associated first scheme identifier according to the device identifier and the second scheme identifier. Furthermore, the associated sets of device identifiers and second scheme identifiers can be queried based on the first scheme identifier.

[0105] For example, let the first scheme identifier be S001. Assume it is associated with two sets of device identifiers and a second scheme identifier. One set of device identifiers and the second scheme identifier are SN001 and D123, respectively, and the other set of device identifiers and the second scheme identifier are SN002 and D456, respectively. Then, the mapping relationship is represented as (S001, SN001, D123), (S001, SN002, D456).

[0106] In the first scenario of the server-side modification scheme, assume that the user terminal requests to modify the S001 treatment scheme stored on the server. Specifically, the user terminal sends a modification request containing SN001 to the server to make the modification and confirm the saving. The server queries the information of SN001, D123, SN002, and D456 based on S001 and the mapping relationship.

[0107] In the second scenario of the device modification scheme, assuming that the treatment device SN001 uploads the modified scheme data of treatment scheme D123, specifically, it sends the modified scheme data and D123, with the scheme data carrying SN001. The server finds S001 based on SN001 and D123, as well as SN002 and D456 associated with S001.

[0108] Step S503: The server synchronizes the modified treatment plan data to the treatment device corresponding to the queried device identifier, so as to update the treatment plan data on the treatment device.

[0109] Continuing with the example above, the principle of step S503 will be explained.

[0110] In the first scenario of modifying the treatment plan on the server side, assume that the user terminal requests to modify the S001 treatment plan stored on the server side. Specifically, the user terminal sends a modification request containing SN001 to the server side to modify and confirm the save. The server side queries the information of SN001, D123, SN002, and D456 according to the mapping relationship based on S001. Further, the server side synchronizes the modified plan data, carrying D123, to the treatment device of SN001, and synchronizes the modified plan data, carrying D456, to the treatment device of SN002. Thus, the synchronous update of the plan data for D123 and D456 is achieved.

[0111] In the second scenario of the device modification scheme, assuming that the treatment device SN001 uploads the modified scheme data of treatment scheme D123, specifically, it sends the modified scheme data and D123, with the scheme data carrying SN001. The server finds S001 based on SN001 and D123, as well as SN002 and D456 associated with S001.

[0112] The following is passed Figure 6 and Figure 7 To explain the above more intuitively Figure 5 The process of synchronously updating the modified scheme data in different embodiments.

[0113] like Figure 6 The diagram illustrates the communication interaction flowchart for data synchronization updates in a modified scheme under a first scenario according to an embodiment of this disclosure. For example, Figure 6 exist Figure 4 Further implementation based on the example.

[0114] exist Figure 6 The process includes:

[0115] Step S601: The user terminal sends a modification scheme request carrying the first scheme identifier S001 to the server.

[0116] Specifically, the user terminal edits and modifies the treatment plan on the service terminal to form the modified plan data.

[0117] Step S602: The server queries the device identifier and the second scheme identifier associated with S001.

[0118] Specifically, you can query the associations of S001 with SN001 and D123, SN002 and D456, and SN003 and D789.

[0119] Step S603: Send the modified scheme data, carrying D123, D456, and D789 respectively, to devices A, B, and C determined by SN001, SN002, and SN003.

[0120] Step S604: Device A, Device C, and Device D respectively verify whether D123, D456, and D789 have corresponding treatment plans locally.

[0121] Step S605: Device A, Device C, and Device D modify the corresponding treatment plans for D123, D456, and D789 locally, respectively.

[0122] Step S606: Device A, Device C, and Device D respectively report the modification results carrying D123, D456, and D789 to the server.

[0123] Step S607: The server notifies the user terminal to modify the result.

[0124] For example, the notification includes treatment plan S001, and D123, D456, and D789 on the treatment device.

[0125] like Figure 7 The diagram illustrates the communication interaction flowchart for data synchronization updates in the modified scheme under the second scenario of an embodiment of this disclosure. For example, Figure 7 exist Figure 4 Further implementation based on the example.

[0126] exist Figure 7 The process includes:

[0127] Step S701: Device A locally modifies the treatment plan.

[0128] Let the second treatment plan be labeled D123.

[0129] Step S702: Device A sends the modified scheme data carrying D123 to the server.

[0130] The solution data may include the device identifier SN001 of device A.

[0131] In some embodiments, the server may perform integrity verification on the received scheme data to ensure its integrity.

[0132] Step S703: The server queries the associated first scheme identifier S001 in the mapping relationship based on D123 and SN001.

[0133] Step S704: The server updates the treatment plan data of S001 according to the modified plan data.

[0134] Step S705: The server synchronizes the updated scheme data (or the modified scheme data) from S001, along with the queried second scheme identifiers D456 and D789, to devices B and C corresponding to the associated device identifiers SN002 and SN003, respectively.

[0135] Subsequently, devices B and C can verify D456 and D789 as in the previous embodiments, update the corresponding solution data, and then return the modified results, similar to the previous embodiments. Figure 7 Redundant information will not be displayed.

[0136] Step S706: The server returns the result of confirming the modified treatment plan D123 to device A.

[0137] Therefore, through the above mapping relationship, it can be ensured that when distributing / synchronizing scheme data, it can be accurately sent to the treatment device that can support the execution of the corresponding treatment scheme.

[0138] In some embodiments, the server can record the distribution status of the protocol data recorded for each treatment plan. The distribution status may include: pending distribution, distribution in progress, distribution completed, distribution failed, confirmed, etc., and may also record the distribution time of each treatment device.

[0139] In some optional embodiments, the server can detect treatment devices with a failed distribution status and perform a distribution retry. When the number of retries or the time reaches a preset condition, failure can be determined, and manual intervention can be notified.

[0140] In some optional embodiments, the server can periodically verify the consistency between its data and the treatment protocol data on the treatment device, and trigger resynchronization when inconsistencies occur. For example, the server can synchronize protocol data that exists on the treatment device but is not stored therein. For example, the server and treatment device can determine the consistency between the protocol data based on the consistency of characteristic information such as the version of the treatment protocol and the summary of the protocol data.

[0141] In some embodiments, before distributing the treatment plan data to each target treatment device, the server may first confirm whether the device configuration of the target treatment device can meet the execution requirements of the treatment plan to be distributed. If not, a conflict exists. The conflict may be between the treatment plan and the treatment device in terms of treatment intensity / performance. For example, if the configuration performance of the target treatment device can only support reaching a certain motion parameter threshold, and the motion parameter range of the task item in the treatment plan's task information exceeds the motion parameter threshold, a conflict exists. Therefore, in some embodiments, the server can modify the motion parameter range in the treatment plan's task information to be below the motion parameter threshold.

[0142] like Figure 8 The diagram shown illustrates a flowchart of an embodiment of the present disclosure, illustrating the device configuration adjustment scheme data based on the target treatment device to be distributed.

[0143] exist Figure 8 In the process of distributing the protocol data to each of the target treatment devices, the procedure includes:

[0144] Step S801: The server obtains the device configuration information of each of the target treatment devices.

[0145] Specifically, the server can query the pre-stored configuration information of the treatment device locally. In an optional example, the device configuration information may include hardware information, such as the model of the treatment device and its performance parameter range. In an optional example, the device configuration may include software information, such as the treatment plan template used on the target treatment device. The treatment plan template provides selection of plan task information; different versions of the treatment plan template may contain different selectable plan tasks, and / or the task execution parameters of the plan tasks may differ. The version can be distinguished by a version number. For example, version 1.0 has plan tasks A and B, version 2.0 adds plan task C, etc., or version 3.0 has improved the medical intensity parameters of A and B compared to version 1.0.

[0146] In some embodiments, the protocol data may include the plan template version number of the applied treatment device, which can be extracted by the server. The server may pre-store the device configuration information and plan template version number of each treatment device. The device configuration information can be obtained by querying based on the plan template version number. Alternatively, the server may obtain the device configuration information by communicating with the target treatment device or by retrieving data from local storage.

[0147] Step S802: In response to the detection of a conflict between the device configuration information of the target treatment device and the protocol data, the server adjusts the protocol data to be compatible with the device configuration information.

[0148] In some optional embodiments, if the server detects a conflict between the device configuration information of the target treatment device and the task execution parameter value of the plan task information in the plan data, the task execution parameter value is modified to adapt to the device configuration information.

[0149] For example, if the range of motion parameters involved in the treatment plan's task information exceeds the threshold of motion parameters that the target treatment device can achieve, the server can modify the range of motion parameters in the treatment plan's task information to be below that threshold.

[0150] In some optional embodiments, if the server detects that there are some functional differences in the device configuration information between the target treatment device and the treatment device that is the source of the solution data, the task items corresponding to the partial functions in the solution task information of the solution data are masked or deleted.

[0151] For example, device A has both upper limb training and cognitive rehabilitation training functions, while device B only has upper limb training functions. Device A will synchronize the treatment plan N, which includes both upper limb training and cognitive rehabilitation training tasks, to the server. When synchronizing treatment plan N to device B, the server can first hide or delete the cognitive rehabilitation training task from the treatment plan N's task information before sending N to device B.

[0152] Step S803: The server distributes the adjusted scheme data to the corresponding target treatment device.

[0153] When dealing with multiple target treatment devices, such as device A, device B, and device C, the server can adjust the solution data according to the device configuration information of each target treatment device to a version that is compatible with device A, device B, and device C respectively, and then distribute it.

[0154] In some embodiments, since the server and each treatment device have the function of modifying the treatment plan data, there may be multiple different plan data for the same treatment plan shared among them, and conflicts may occur between the multiple different plan data.

[0155] To resolve this conflict, such as Figure 9 The diagram shown illustrates a flowchart of a conflict resolution mechanism in one embodiment of this disclosure.

[0156] exist Figure 9 The process includes:

[0157] Step S901: The server receives the treatment plan data sent by the treatment device when creating or modifying the treatment plan.

[0158] Step S902: The treatment device compares data from multiple treatment protocols belonging to the same treatment protocol to determine whether there is a conflict.

[0159] Step S903: In response to the existence of a conflict, the server identifies the conflict type based on the conflicting data items in the multiple protocol data of the same treatment protocol and / or the device to which the conflicting protocol data belongs.

[0160] Step S904: The server determines the applicable conflict resolution strategy based on the identified conflict type, and resolves the conflict through the conflict resolution strategy.

[0161] In some embodiments, the solution data includes basic solution information, solution task information, and timestamps. Specifically, each task in the basic solution information and solution task information may have a timestamp indicating its creation / modification. By determining whether the conflicting data of multiple solutions per treatment plan belong to the same device (e.g., between the server and the treatment device, or between treatment devices), and the type of conflicting data items (e.g., conflict of basic information, or conflict of task items), the conflict type is determined, and a corresponding conflict resolution strategy is established.

[0162] In some embodiments, the conflict resolution strategy includes at least one of the following: timestamp priority strategy, server-side priority strategy, and merging strategy.

[0163] As an example, the timestamp priority strategy, applicable to a first conflict type where multiple treatment devices modify basic protocol information, is implemented by retaining the protocol data with the newest timestamp among the conflicting protocol data. Specifically, among multiple protocol data with conflicting basic protocol information, the protocol data with the newest basic protocol information is prioritized.

[0164] As an example, the server-side priority strategy, applicable to a second type of conflict where there is a conflict between protocol data created on the server side and protocol data provided by the treatment device, is implemented by prioritizing the protocol data created on the server side. Specifically, since the treatment device may periodically update with the server while online, the version of the protocol data on the server side will be prioritized among multiple protocol data sets that have conflicting basic protocol information.

[0165] As an example, the merging strategy is applicable to a third conflict type where multiple treatment devices modify protocol task information, updating the modifications made by each treatment device to the protocol data in timestamp order. Specifically, if the protocol task information corresponds to modifications of parameters for a treatment task, which may be adaptive adjustments to the patient's physical condition, then the modifications to the protocol task information can be updated in timestamp order.

[0166] like Figure 10 The diagram illustrates a flowchart of the application of a treatment plan using a treatment device in one embodiment of this disclosure. The treatment plan can be distributed by the server in previous embodiments, or it can be created / modified locally.

[0167] exist Figure 10 The process includes:

[0168] Step S1001: The treatment device displays data for the various available treatment options;

[0169] Step S1002: In response to the user's application operation on the protocol data, the treatment device generates a medical task based on the operated protocol data for execution.

[0170] In some embodiments, the treatment device can adjust the treatment plan's task information according to the patient's physical condition. Therefore, optionally, before step S1001, the process may further include:

[0171] Step S1003: Obtain the patient identifier of the patient using the treatment device, and query the patient's physical condition data based on the patient identifier.

[0172] Step S1004: Query the scheme data that has task execution parameter values ​​that match the physical condition data.

[0173] The matching refers to the matching of the patient's physical condition represented by the physical condition data with the medical intensity represented by the task execution parameter values.

[0174] like Figure 11 The diagram shows a schematic of a data distribution device for a treatment plan according to an embodiment of this disclosure. It should be noted that the principle and technical implementation of the data distribution device for the treatment plan can refer to the data distribution method for the treatment plan in previous embodiments, therefore, it will not be repeated in this embodiment.

[0175] The data distribution device 1100 for the treatment plan includes:

[0176] The distribution confirmation module 1101 is used to respond to the user's confirmation operation on the treatment plan data, store the plan data, and provide a set of candidate treatment devices applicable to the treatment plan;

[0177] The target device distribution confirmation module 1102 is used to distribute the plan data to each of the target treatment devices in response to a user selecting one or more target treatment devices from the set of candidate treatment devices.

[0178] The mapping relationship establishment module 1103 is used to establish a mapping relationship between the treatment plan and the one or more target treatment devices; the mapping relationship is used to determine the synchronization object when the plan data of the treatment plan is modified.

[0179] It should be noted that, in Figure 11 The various functional modules in the embodiments can be implemented, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, they can be implemented, in whole or in part, in the form of a computer program or instruction product. A computer program or instruction product includes one or a set of computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, they generate, in whole or in part, the processes or functions according to this disclosure. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another.

[0180] and, Figure 11 The apparatus disclosed in the embodiments can be implemented through other modular division methods. The apparatus embodiments shown above are merely illustrative. For example, the module division is only a logical functional division, and in actual implementation, there may be other division methods. For example, a group of modules or modules may be combined or dynamically integrated into another system, or some features may be ignored or not executed. Furthermore, the shown or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces, and the indirect coupling or communication connection between devices or modules may be electrical or other forms.

[0181] in addition, Figure 11 The functional modules and sub-modules in the embodiments can be dynamically integrated within a single processing unit, or each module can exist physically independently, or two or more modules can be dynamically integrated within a single unit. These dynamic units can be implemented in hardware or as software functional modules. If these dynamic units are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. This storage medium can be a read-only memory, a hard disk, or an optical disk, etc.

[0182] It should be specifically noted that the flowchart representations of the embodiments described above in this disclosure can be understood as representing modules, segments, or portions of code comprising one or more sets of executable instructions configured to implement specific logical functions or processes. Furthermore, the scope of the preferred embodiments of this disclosure includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved.

[0183] For example, Figures 2 to 9 The order of the steps in the method embodiments may vary in specific scenarios and is not limited to the above representation.

[0184] like Figure 12 The diagram shown illustrates the structure of a computer device according to an embodiment of the present disclosure.

[0185] The server, treatment equipment, and user terminal can be implemented based on the computer device 1200 in this embodiment.

[0186] The computer device 1200 includes a bus 1201, a processor 1202, and a memory 1203. The processor 1202 and the memory 1203 can communicate via the bus 1201. The memory 1203 can store computer programs or instructions. The processor 1202 implements the method flow or function of the previous embodiments by running the computer program or instructions in the memory 1203, for example... Figure 2 wait.

[0187] Bus 1201 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of representation, although only one thick line is used in the diagram, this does not indicate that there is only one bus or one type of bus.

[0188] In some embodiments, the processor 1202 may be implemented as a central processing unit (CPU), a microprocessor unit (MCU), a system-on-chip (System-on-Chip), or a field-programmable array (FPGA). The memory 1203 may include volatile memory for temporary data storage during program execution, such as random access memory (RAM).

[0189] The memory 1203 may also include non-volatile memory for data storage, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid-state disk (SSD).

[0190] In some embodiments, the computer device 1200 may further include a communicator 1204. The communicator 1204 is used for communication with external devices. In specific examples, the communicator 1204 may include one or more wired and / or wireless communication circuit modules. For example, the communicator 1204 may include one or more of, such as a wired network card, a USB module, a serial interface module, etc. The wireless communication protocols followed by the wireless communication module include, for example, Nearfield communication (NFC) technology, Infrared (IR) technology, Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time-Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), Bluetooth (BT), Global Navigation Satellite System (GNSS), etc.

[0191] This disclosure also provides a computer-readable storage medium storing a computer program or instructions, which, when run, implement the method flow or function of any of the previous embodiments.

[0192] That is, the method steps in the above embodiments are implemented as software or computer code that can be stored in a recording medium (such as CD ROM, RAM, floppy disk, hard disk or magneto-optical disk), or implemented as computer code that is originally stored in a remote recording medium or a non-transitory machine-readable medium and will be stored in a local recording medium after being downloaded via a network, so that the method represented herein can be stored in such software processing on a recording medium using a general-purpose computer, a special processor or programmable or special hardware (such as ASIC or FPGA).

[0193] This disclosure may also provide a computer program product, comprising one or more computer programs or instructions, which, when run, perform all or part of the method flows or functions of this disclosure. The computer program product includes one or more computer programs or instructions.

[0194] Computer programs or instructions can be stored in a readable storage medium or transferred from one readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The readable storage medium can be any available medium capable of access, or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; an optical medium, such as a digital video optical disc; or a semiconductor medium, such as a solid-state drive. The computer-readable storage medium can be a volatile or non-volatile storage medium, or it can include both volatile and non-volatile types of storage media.

[0195] In summary, this disclosure relates to the field of medical data processing technology, providing a data distribution method, computer device, and storage medium for treatment plans. The method includes: a server responding to a user's confirmation operation on the treatment plan data, storing the plan data, and providing a set of candidate treatment devices applicable to the treatment plan; the server responding to a user selecting one or more target treatment devices from the set of candidate treatment devices, distributing the plan data to each of the target treatment devices; the server establishing a mapping relationship between the treatment plan and the one or more target treatment devices; the mapping relationship being used to determine the synchronization object when the treatment plan data is modified. Therefore, this disclosure achieves the screening of applicable treatment devices based on the treatment plan, automatically completing the distribution of plan data to batch devices, and providing a synchronization mechanism during modifications, effectively solving problems in related technologies, improving the distribution efficiency of treatment plans, reducing errors, and achieving efficient synchronization during plan modifications.

[0196] Compared with related technologies, the solutions in the above embodiments of this disclosure can achieve the following beneficial effects:

[0197] 1. Automatic distribution of treatment plan data: Through synchronization from treatment devices to the server and batch distribution from the server to devices, the automatic flow of treatment plan data among multiple treatment devices is realized, eliminating the need for manual configuration of each device and greatly improving efficiency.

[0198] 2. Ensure data consistency: Through change detection and automatic distribution mechanisms, when any treatment device modifies the shared protocol, the changes will be automatically synchronized to all relevant devices, ensuring that the protocol data on the relevant devices remains consistent.

[0199] 3. Supports unified server-side management: Treatment plans can be created / edited uniformly and distributed to multiple devices in batches through the server, realizing centralized management and unified distribution of plan data, which facilitates the management and maintenance of plans.

[0200] 4. Intelligent Device Type Matching: Through device type identification and matching mechanisms, the system ensures that the treatment plan is only distributed to compatible devices of the same type, thus avoiding the problem that the treatment plan data cannot be used on inapplicable treatment devices.

[0201] 5. Effective conflict resolution: Through multiple conflict resolution strategies, it can intelligently handle conflicts when multiple devices modify the scheme simultaneously, ensuring the correctness and integrity of the data.

[0202] 6. Reliable distribution mechanism: Through distribution confirmation, status tracking and failure retry mechanism, the reliability of solution data distribution is ensured, avoiding the problems of data loss or distribution failure.

[0203] The above embodiments are merely illustrative of the principles and effects of this disclosure and are not intended to limit this disclosure. Any person skilled in the art can modify or alter the above embodiments without departing from the spirit and scope of this disclosure. Therefore, all equivalent modifications or alterations made by those skilled in the art without departing from the spirit and technical concept disclosed in this disclosure should still be covered by the protection scope of this disclosure.

Claims

1. A method for distributing data on a treatment plan, characterized in that, include: In response to the user's confirmation of the treatment plan data, the server stores the treatment plan data and provides a set of candidate treatment devices applicable to the treatment plan. The server responds to the user's selection of one or more target treatment devices from the set of candidate treatment devices by distributing the plan data to each of the target treatment devices. The server establishes a mapping relationship between the treatment plan and the one or more target treatment devices; the mapping relationship is used to determine the synchronization object when the treatment plan data is modified.

2. The data distribution method for the treatment plan according to claim 1, characterized in that, The server responds to the user's confirmation of the treatment plan data, stores the plan data, and provides a set of candidate treatment devices applicable to the treatment plan, including: In response to a user's request to create / edit a treatment plan on the server, a graphical interface is provided for creating / editing the treatment plan data; In response to the user's confirmation of the treatment plan data, the set of applicable alternative treatment devices associated with the treatment plan is displayed.

3. The data distribution method for the treatment plan according to claim 1 or 2, characterized in that, The method for determining the type of equipment applicable to the treatment plan includes at least one of the following: 1) Determined based on the device type selected by the user when creating a treatment plan on the server side; 2) Receive the treatment plan data created and sent by the treatment device, and query the device type of the treatment device based on the device identifier of the treatment device extracted from the plan data, which is the applicable device type of the treatment plan.

4. The data distribution method for the treatment plan according to claim 1, characterized in that, The server-side establishes a mapping relationship between the treatment plan and the one or more target treatment devices, including: The server assigns a first scheme identifier to the treatment plan and establishes a mapping relationship between the first scheme identifier and the device identifier of each target treatment device; the first scheme identifier is used to distribute to each target treatment device along with the scheme data; The server obtains a first scheme identifier and a second scheme identifier from each target treatment device that receives the scheme data; wherein the second scheme identifier is assigned by the target treatment device to the treatment scheme. The server establishes a mapping relationship between the first scheme identifier and the second scheme identifier of each target treatment device.

5. The data distribution method for the treatment plan according to claim 4, characterized in that, Also includes: The server obtains treatment plan modification information, which includes modified plan data and a first plan identifier or a second plan identifier. The solution data carries the device identifier of the treatment equipment; The server obtains the first identifier, or determines the first identifier based on the second identifier and the device identifier in the scheme data through the mapping relationship, and queries the device identifier of each treatment device associated with the first scheme identifier in the mapping relationship based on the first identifier; The server synchronizes the modified treatment plan data to the treatment device corresponding to the queried device identifier, so as to update the treatment plan data on the treatment device.

6. The data distribution method for the treatment plan according to claim 5, characterized in that, The server-side acquisition of treatment plan modification data includes at least one of the following: 1) The server obtains a scheme modification request initiated by the user, the modification request including the modified scheme data and the first scheme identifier; 2) The server receives a scheme modification data packet from the current treatment device. The scheme modification data packet contains the modified scheme data and the second scheme identifier; wherein the current treatment device is excluded from the synchronized treatment devices.

7. The data distribution method for the treatment plan according to claim 1, characterized in that, Before distributing the protocol data to each of the target treatment devices, the method further includes: The server obtains the device configuration information of each of the target treatment devices; The server responds to the detection of a conflict between the device configuration information of the target treatment device and the protocol data by adjusting the protocol data to be compatible with the device configuration information. The server distributes the adjusted treatment plan data to the corresponding target treatment device.

8. The data distribution method for the treatment plan according to claim 1, characterized in that, Also includes: The server receives the treatment plan data sent by the treatment device when creating or modifying the treatment plan; The treatment device compares data from multiple treatment protocols belonging to the same protocol to determine if there are any conflicts. In response to the existence of a conflict, the server identifies the conflict type based on conflicting data items in multiple treatment plan data for the same treatment plan and / or the device to which the conflicting treatment plan data belongs; The server determines the applicable conflict resolution strategy based on the identified conflict type, and resolves the conflict using the conflict resolution strategy.

9. The data distribution method for the treatment plan according to claim 8, characterized in that, The solution data includes basic solution information, solution task information, and timestamps. The conflict resolution strategy includes at least one of the following: timestamp priority strategy, server-side priority strategy, and merging strategy; The timestamp priority strategy, applicable to the first conflict type where multiple treatment devices modify basic protocol information, is implemented to retain the protocol data with the newest timestamp among the protocol data involved in the conflict. The server-side priority policy applies to a second type of conflict where there is a conflict between the protocol data created on the server and the protocol data provided by the treatment device, and is implemented to prioritize retaining the protocol data created on the server. The merging strategy is applicable to the third conflict type where multiple treatment devices modify the plan task information, and updates the modified content of each treatment device to the plan data in the order of timestamps.

10. The data distribution method for the treatment plan according to claim 7, characterized in that, The scheme data includes a plan template version number so that it can be extracted by the server, and the device configuration information includes a plan template for selecting scheme task information; or, the server obtains the device configuration information by communicating with the target treatment device or from locally stored data.

11. The data distribution method for the treatment plan according to claim 7, characterized in that, The step of adjusting the protocol data to be compatible with the device configuration information when a conflict is detected between the target treatment device's configuration information includes at least one of the following: 1) In response to the detection of a conflict between the device configuration information of the target treatment device and the task execution parameter value of the protocol task information in the protocol data, the task execution parameter value is modified to adapt to the device configuration information; 2) In response to the detection that there are some functional differences in the device configuration information between the target treatment device and the treatment device that is the source of the solution data, the task items corresponding to the relevant functional differences in the solution task information of the solution data are masked or deleted.

12. The data distribution method for treatment plans according to claim 1, characterized in that, Also includes: The treatment device displays data for various available treatment options; In response to the user's application of the protocol data, the treatment device generates medical tasks based on the processed protocol data for execution.

13. The data distribution method for the treatment plan according to claim 12, characterized in that, Before the treatment device displays data on the various available treatment options, it also includes: Obtain the patient identifier of the patient using the treatment device, and query the patient's physical condition data based on the patient identifier; Query the solution data that has task execution parameter values ​​that match the physical condition data; wherein, the matching means that the patient's physical condition represented by the physical condition data matches the medical intensity represented by the task execution parameter values.

14. The data distribution method for treatment plans according to claim 1, characterized in that, It also includes at least one of the following: 1) Record the distribution status of the treatment plan data for each treatment plan; 2) For treatment devices whose distribution status is failed, perform a distribution retry; 3) Periodically verify the consistency of treatment plan data between the server and the treatment device, and trigger resynchronization when inconsistencies occur.

15. A computer device, characterized in that, include: Processor and memory; The memory stores computer programs or instructions; The processor is configured to run the computer program or instructions to perform the data distribution method for the treatment regimen as described in any one of claims 1 to 14.

16. A computer-readable storage medium, characterized in that, A data distribution method that stores a computer program or instructions, which are executed to perform a treatment regimen as described in any one of claims 1 to 14.

Images