Hierarchical medical data hierarchical processing method and system supporting multi-party authorization

Abstract

The invention discloses a hierarchical medical data hierarchical processing method supporting multi-party authorization, and the method comprises the following steps: carrying out basic geometric transformation on original medical data, employing a spherical coordinate mapping mode for the basic geometric transformation, and mapping the original medical data into a spherical coordinate system; corresponding conversion level secret keys are distributed to different types of authorization parties, the authorization parties at least comprise a patient, a family doctor and an emergency contact person, and the conversion level secret keys of the different types of authorization parties correspond to different data access permissions. The method has the beneficial effects that in the technical scheme, through hierarchical quadratic geometric transformation and differential keys, 'minimum permission 'access of patients, doctors and contacts is realized, and data requirements of different roles are met; the geometric transformation technology of spherical coordinate mapping and ellipse cutting is adopted, complexity of traditional encryption is avoided, and meanwhile data leakage is prevented through secret key isolation and dynamic adjustment.

Description

Technical Field

[0001] This invention relates to the field of data security and privacy protection technology, and in particular to a method and system for hierarchical medical data processing that supports multi-party authorization. Background Technology

[0002] With the rapid development of medical informatization and telemedicine technologies, the sharing and utilization of electronic health records (EHRs) and real-time physiological monitoring data (such as electrocardiograms, blood pressure, and blood oxygen saturation) have become key supports for improving the efficiency of medical services. However, medical data contains a large amount of personal privacy information (such as patient identity, medical history, and physiological characteristics), and its security protection and authorized access control have always been core challenges facing the industry.

[0003] In existing technologies, authorization management of medical data mainly relies on role-based access control (RBAC) or traditional data encryption technologies (such as symmetric encryption and asymmetric encryption). However, these methods have the following significant drawbacks in practical applications: Insufficient granularity of permission division: Traditional RBAC models typically assign permissions based on fixed roles (such as "doctor" and "patient"), which cannot provide fine-grained data access scope according to the specific needs of the authorizing party (such as diagnosis, emergency assistance, routine viewing, etc.), leading to problems of "excessive permissions" or "insufficient permissions"—for example, a family doctor may obtain more private data than necessary for diagnosis, while emergency contacts may not be able to quickly obtain critical status information in critical situations.

[0004] Low data conversion and restoration efficiency: Traditional encryption technology requires overall encryption and decryption of data, which is a complex process with high computational overhead. It is difficult to meet the needs of rapid analysis of real-time monitoring data in remote medical scenarios, especially in emergency medical response where decryption delays may affect treatment efficiency.

[0005] Lack of dynamic permission adjustment capability: In dynamic scenarios such as changes in patient condition (e.g., from stable to critical), changes in the identity of the authorizing party (e.g., changing family doctors), or adjustments to the emergency contact list, the existing system cannot automatically trigger permission updates and requires manual intervention, resulting in lagging permission management or security vulnerabilities.

[0006] Lack of medical data characteristic adaptation mechanism: Medical data contains multiple types of information, such as structured physiological parameters (e.g., heart rate, blood pressure), unstructured waveform data (e.g., electrocardiogram waveforms), and status indicators (e.g., abnormal alarms). Existing technologies have not designed protection schemes for their heterogeneity, making it difficult to preserve the medical diagnostic value of the data while protecting privacy.

[0007] Therefore, how to achieve refined authorization management, dynamic permission adjustment, and efficient and secure conversion of medical data, while protecting patient privacy and meeting the differentiated needs of different authorized parties (such as the patient, family doctor, and emergency contact), has become a pressing technical problem in the field of medical data security. Summary of the Invention

[0008] The main technical problem solved by this invention is to provide a hierarchical medical data processing method and system that supports multi-party authorization, thereby solving one or more of the problems in the prior art.

[0009] To solve the above-mentioned technical problems, the present invention adopts a technical solution as follows: a hierarchical medical data processing method supporting multi-party authorization, the innovation of which is: including the following steps: A basic geometric transformation is performed on the original medical data, which uses a spherical coordinate mapping method to map the original medical data into a spherical coordinate system; Assign corresponding conversion level keys to different types of authorized parties, including at least the patient, family doctor, and emergency contact, and the conversion level keys for different types of authorized parties correspond to different data access permissions; Based on the results of the basic geometric transformation, a hierarchical secondary geometric transformation is performed. Each level of secondary geometric transformation corresponds to the access rights of an licensor, and the secondary geometric transformations at different levels are independent of each other. It dynamically adjusts the hierarchical permissions of different authorized parties in response to preset trigger conditions.

[0010] In some implementations, the permissions of the conversion level key include: the patient's own key is the complete inverse conversion parameter, which can restore all the original medical data; The family doctor's key can only decipher the critical parameters used for diagnosis; The emergency contact's key can only decipher the abnormal status identifier.

[0011] In some implementations, the hierarchical quadratic geometric transformation includes elliptical cutting of the spherical coordinate mapping result, and defining the data range accessible to different authorized parties by pre-defined elliptical parameters.

[0012] In some implementations, key parameters for diagnosis include physiological signal waveforms with privacy tags removed, which include at least one or more of heart rate waveforms and respiratory waveforms.

[0013] In some implementations, the abnormal status identifier includes a Boolean status value obtained from the analysis of raw medical data, which is used to identify at least one or more of "abnormal heart rate" and "abnormal blood pressure".

[0014] In some implementations, the preset triggering conditions include at least one of the following: changes in the patient's condition level, changes in the family doctor's identity, and adjustments to the emergency contact list.

[0015] A hierarchical geometry transformation system supporting multi-party authorization includes: The basic transformation module is configured to perform basic geometric transformations on the original medical data using spherical coordinate mapping and output the spherical coordinate mapping results. The key allocation module is configured to allocate corresponding conversion level keys to different types of authorized parties. The authorized parties include at least the patient, family doctor, and emergency contact, and the conversion level keys of different types of authorized parties correspond to different data access permissions. The hierarchical transformation module is configured to perform hierarchical quadratic geometric transformations based on the spherical coordinate mapping results. Each level of quadratic geometric transformation corresponds to the access permissions of an authorized party, and the transformation parameters of each level are isolated from each other. The permission adjustment module is configured to dynamically update the hierarchical permissions of different authorized parties and the corresponding conversion level keys based on preset trigger conditions.

[0016] In some implementations, the conversion level key permissions assigned by the key allocation module include: The patient's own key is a complete inverse transformation parameter, which can restore all the original medical data through inverse operation; The family doctor's key is associated with the decryption algorithm for key parameters used in diagnosis; The emergency contact's key is associated with the decryption algorithm for the abnormal status identifier.

[0017] In some implementations, the hierarchical transformation performed by the hierarchical transformation module includes elliptical cutting of the spherical coordinate mapping result, and the data access range of different levels is defined by adjusting the semi-axis length and rotation angle parameters of the ellipse.

[0018] In some implementations, the preset triggering conditions for the permission adjustment module include at least one of the following: a worsening or improvement in the patient's condition, a change in the family doctor contract relationship, or the expiration of the authorization period for the emergency contact.

[0019] The beneficial effects of this invention are: Fine-grained access control: Through hierarchical quadratic geometric transformation and differentiated keys, patients, doctors, and contacts can access data with "least privileges" to meet the data needs of different roles; High security: It adopts geometric transformation technology of spherical coordinate mapping and ellipse cutting to avoid the complexity of traditional encryption, and prevents data leakage through key isolation and dynamic adjustment; Dynamic adaptability: Quickly adjust permissions in response to changes in the patient's condition, changes in the authorized party, etc., to ensure data availability in emergency situations; Medical Applicability: Specifically designed for the characteristics of medical data, it retains the key parameters necessary for diagnosis while removing privacy markers, balancing medical applications and privacy protection; High efficiency: The geometric transformation algorithm has low computational cost and can be efficiently deployed in medical devices and systems without affecting real-time data processing and analysis. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort, wherein: Figure 1 This is a flowchart of a hierarchical medical data processing method that supports multi-party authorization, according to the present invention.

[0021] Figure 2 This is a flowchart of a hierarchical geometry transformation system that supports multi-party authorization according to the present invention.

[0022] Figure 3 This is a schematic diagram of spherical coordinate mapping and elliptical cutting in an embodiment of the present invention. Detailed Implementation

[0023] The technical solutions in the embodiments of the present invention will be clearly and completely described below. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of them. 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.

[0024] I. Specific implementation of a hierarchical medical data processing method supporting multi-party authorization (e.g.) Figure 1 ) 1.1 Basic Geometric Transformations A fundamental geometric transformation is performed on the original medical data, mapping it to a spherical coordinate system. The specific process is as follows: Raw medical data may include the patient's physiological monitoring data (such as electrocardiogram data, blood pressure data, blood oxygen saturation data, etc.), and its parameters are initially represented as points (x, y, z) in a Cartesian coordinate system. The Cartesian coordinates are then transformed into points (r, θ, φ) in a spherical coordinate system using a coordinate transformation formula, where: Radius r: Calculated by weighting multiple parameters in the original data (e.g., diastolic blood pressure × 0.6 + blood oxygen saturation value × 0.4, where blood oxygen saturation is the percentage part, such as 98% corresponding to 98). Polar angle θ: obtained from heart rate data, the conversion formula is θ = heart rate value × (π / 180) (e.g., heart rate of 72 beats / minute corresponds to θ = 72 × (π / 180) = 1.256 radians); Azimuth angle φ: obtained from systolic blood pressure data, the conversion formula is φ = systolic blood pressure × (π / 200) (e.g., systolic blood pressure of 120 mmHg corresponds to φ = 120 × (π / 200) = 1.885 radians).

[0025] Example: The original medical data is a patient's continuous 5-minute ECG monitoring data, including heart rate [72,73,71,75,74] beats / minute, systolic blood pressure [120,122,118,125,123] mmHg, diastolic blood pressure [80,81,79,82,81] mmHg, and blood oxygen saturation [98%,97%,98%,99%,98%]. After the above transformation, the spherical coordinate data are (87.2,1.256,1.885), (88.0,1.274,1.916), (86.4,1.240,1.854), (89.6,1.309,1.963), (88.8,1.292,1.934) (unit: arbitrary length units).

[0026] 1.2 Conversion Level Key Distribution Assign corresponding conversion-level keys to different types of authorized parties, including the patient, family doctor, and emergency contact. Specific key permissions are as follows: For the patient: The key contains complete inverse transformation parameters, including a full set of transformation parameters from spherical coordinates to Cartesian coordinates (such as the inverse transformation matrix [[1.2,0.3],[0.5,2.1]] and the offset (0.02,0.03)), which can restore all the original medical data through inverse operations; Family Doctor: The key contains some inverse transformation parameters and filtering algorithms (such as the decryption function f(x)=a×sin(x)+b, where a=0.8, b=0.15), which can only decipher the key parameters used for diagnosis (such as de-anonymized heart rate waveform, blood pressure fluctuation curve, time axis anonymization and removal of patient identifiers). Emergency Contact: The key contains the threshold set required for abnormal status judgment (such as abnormal heart rate threshold [<60,>100], abnormal blood pressure threshold [systolic blood pressure>140, diastolic blood pressure>90]) and Boolean value generation function g(x)=1 if x∈abnormal interval else0, which can only solve for abnormal status identifiers (such as [normal heart rate: True, normal blood pressure: True]).

[0027] 1.3 Layered Quadratic Geometric Transformation Based on the results of the fundamental geometric transformation, a hierarchical secondary geometric transformation is performed. Each transformation corresponds to a different access permission level for the authorized party, and they are independent of each other. Specifically, ellipse cutting is used, and the data access range is defined by preset ellipse parameters. Patient level: Ellipse parameters are set to major semi-axis = 100, minor semi-axis = 80, rotation angle = 0°, covering the entire spherical coordinate space, making all data accessible; Family doctor level: The ellipse parameters are set to major semi-axis = 60, minor semi-axis = 45, rotation angle = 30°, and the core data area containing heart rate and blood pressure trends is extracted, retaining only the key parameters necessary for diagnosis (such as heart rate waveform, respiratory waveform and other physiological signal waveforms). Emergency contact level: The ellipse parameters are set to major semi-axis = 20, minor semi-axis = 15, rotation angle = 0°, retaining only the extreme point data required for abnormal status judgment, and outputting a Boolean abnormal status indicator.

[0028] 1.4 Dynamic Adjustment of Hierarchical Permissions Permissions are dynamically adjusted in response to preset trigger conditions. The specific trigger conditions and adjustment methods are as follows: Changes in patient condition severity: If a patient's heart rate rises from 72 beats / minute to 105 beats / minute (>100 beats / minute abnormal threshold) or systolic blood pressure rises to 145 mmHg (>140 mmHg abnormal threshold), the "condition worsens" condition is triggered. The ellipse parameters of the emergency contact are temporarily adjusted to semi-major axis = 30 and semi-minor axis = 25. An abnormal occurrence timestamp field is added to decrypt the abnormal trend data of the past 30 minutes. Change of family doctor status: When a patient changes family doctors, the system automatically revokes the original doctor's key permissions and assigns a family doctor level key to the new doctor; Emergency contact list adjustment: When adding or deleting emergency contacts, the system will assign or revoke their key permissions accordingly to ensure that only contacts in the current list can access the abnormal status indicator.

[0029] Based on the dual dimensions of "indicator value + duration", the trigger thresholds for escalation / regression of each disease level are clearly defined, as follows: physiological indicators Quantitative indicator thresholds (including time conditions) Corresponding level jump Heart rate 1. Heart rate > 100 beats / min for ≥ 5 minutes → Upgrade from Level 1 to Level 2. 2. Heart rate > 110 beats / min for ≥ 3 minutes → Upgrade from Level 2 to Level 3. 3. Heart rate > 130 beats / min or < 40 beats / min, triggered in a single occurrence → Upgrade from any level to Level 4. 4. Heart rate recovers to 60-100 beats / min for ≥ 24 hours → Revert from Level 2 / 3 to Level 1. 1→2; 2→3; any→4; 2 / 3→1 blood pressure 1. Systolic blood pressure >140 mmHg or <90 mmHg for ≥10 minutes → Grade 1 upgraded to Grade 2. 2. Systolic blood pressure >150 mmHg or <80 mmHg for ≥5 minutes → Grade 2 upgraded to Grade 3. 3. Systolic blood pressure >170 mmHg or <70 mmHg, triggered in a single instance → Any grade upgraded to Grade 4. 4. Systolic blood pressure recovers to 90-140 mmHg and persists for ≥24 hours → Grade 2 / 3 downgraded to Grade 1. 1→2; 2→3; any→4; 2 / 3→1 II. Specific implementation of a hierarchical geometric transformation system supporting multi-party authorization (e.g.) Figure 2 ) 2.1 System Composition This system includes a basic conversion module, a key distribution module, a hierarchical conversion module, and a permission adjustment module. These modules work together to implement the above methods.

[0030] 2.2 Basic Conversion Module Configured to perform spherical coordinate mapping on raw medical data: Input raw medical data (such as ECG monitoring data, physiological signal waveforms, etc.), map it to a spherical coordinate system using coordinate transformation formulas (as described in 1.1), and output the spherical coordinate mapping result in the form of (r, θ, φ). For example, after processing 5 minutes of ECG monitoring data, the output is spherical coordinate data such as (87.2, 1.256, 1.885).

[0031] 2.3 Key Distribution Module Configured to assign transformation level keys to different authorized parties: Based on the authorized party type (patient, family doctor, emergency contact), a preset key generation algorithm is invoked to assign keys corresponding to the permissions. For example: generate a key containing the complete inverse transformation matrix and offset for patients; generate a key with an association screening algorithm (e.g., f(x) = 0.8 × sin(x) + 0.15) for family doctors; and generate a key with an association threshold set and a Boolean function (e.g., g(x)) for emergency contacts.

[0032] 2.4 Layered Conversion Module The configuration is set to perform a hierarchical quadratic geometric transformation based on the spherical coordinate mapping results: An ellipse cutting algorithm is invoked to cut the spherical coordinate data according to the preset ellipse parameters (such as the major and minor axes and rotation angles) of each authorized party, outputting hierarchical data accessible to each authorized party. For example, after cutting the family doctor level, de-anonymized heart rate waveforms and blood pressure fluctuation curves are output; after cutting the emergency contact level, Boolean abnormal status indicators are output.

[0033] 2.5 Permission Adjustment Module Configured to dynamically update permissions based on preset trigger conditions: Real-time monitoring of patient condition data (such as heart rate and blood pressure) and authorized party information (such as family doctor contract relationship and emergency contact list). When the trigger conditions are met (such as worsening of condition, doctor change, or contact adjustment), the ellipse parameters and key permissions of the corresponding authorized party are automatically updated, with an adjustment response time of <0.5 seconds, and the data transmission encryption strength is maintained at AES-256 level.

[0034] The permission adjustment execution process includes the following steps: 1. Trigger detection Monitoring targets: physiological indicators (heart rate, blood pressure, etc.), authorized party information (doctor contract relationship, contact list), and time thresholds (such as abnormal duration).

[0035] Detection logic: The system's real-time acquisition module (sampling frequency ≥ 1 time / second) compares the current data with a preset threshold (e.g., heart rate > 130 beats / min triggers level 4 upgrade).

[0036] 2. System Evaluation Evaluation subject: Permission decision engine.

[0037] Output content: Automatically match permission templates based on the severity of illness (e.g., level 4 illness corresponds to emergency contact permission upgrade), and generate adjustment schemes (e.g., ellipse parameters change from 20 to 30 on the major semi-axis).

[0038] 3. Notification Confirmation a. Tiered notification: Routine adjustments (e.g., upgrading from level 2 to level 3): Send a confirmation request to the patient (via APP / SMS), and automatically execute if there is no response within 15 minutes; Emergency adjustments (e.g., level 4 upgrade): Skip patient confirmation, proceed directly, and record supplementary instructions within 24 hours afterwards.

[0039] 4. Parameter update Execution entities: Key management module and hierarchical conversion module.

[0040] Effective time: Parameter update response time is less than 0.5 seconds, and permission adjustments take effect immediately.

[0041] 5. Log recording Record content: trigger time, reason for adjustment, participating parties (e.g., "patient XXX confirmed"), parameters before and after adjustment, effective duration.

[0042] Security requirements: Logs must be immutable and support hospital privacy compliance audits.

[0043] For the following specific scenarios, implement differentiated process adaptation: Level 1-4 Emergency Upgrade Triggering conditions: Heart rate >130 bpm or <40 bpm (single occurrence), systolic blood pressure >170 mmHg or <70 mmHg (single occurrence).

[0044] Processing logic: Skip patient confirmation, the system automatically upgrades the emergency contact's permissions to temporary diagnostic level (access to trend data for the past 30 minutes), and sends an emergency notification to the patient's family.

[0045] 2. Permission rollback Triggering condition: The condition returns to level 1 (e.g., heart rate recovers to 60-100 beats / min and lasts for ≥24 hours).

[0046] Processing logic: The system automatically rolls back permission parameters (e.g., ellipse parameters from the major semi-axis 30 to 20), and synchronously records the reason for the rollback (e.g., "condition has improved to a stable period").

[0047] 3. Conflicts among multiple authorized parties Example scenario: The patient has not confirmed the permission adjustment, but the family doctor needs to temporarily access the data due to emergency needs.

[0048] Processing logic: The system generates a temporary authorization code valid for 1 hour (entered by the doctor to obtain permission), triggers a real-time notification to the patient, and marks it as "emergency authorization" in the log afterwards.

[0049] The working principle of this technical solution is as follows: This invention achieves multi-party authorized hierarchical medical data processing through a collaborative mechanism of "basic geometric transformation → hierarchical secondary transformation → key allocation → dynamic adjustment": Basic geometric transformation: Mapping the raw medical data to a spherical coordinate system, preserving the data topology while laying the foundation for hierarchical processing; Layered secondary transformation: Through independent ellipse cutting, differentiated data access scopes are defined for different authorized parties to ensure permission isolation; Key distribution: Assign keys of corresponding levels to each authorized party to achieve "decryption on demand" (patients restore all data, doctors decrypt diagnostic parameters, and contacts decrypt abnormal indicators); Dynamic adjustment: Based on triggering conditions such as changes in the patient's condition or changes in the authorized party, permissions are updated in real time to balance data security and emergency needs.

[0050] Dynamic adaptability: Responds quickly to changes in patient condition, changes in authorized parties, etc., and adjusts permissions quickly (response time < 0.5 seconds) to ensure data availability in emergency situations; supports automatic matching of "patient condition level - permission template" (e.g., automatically activating temporary diagnosis permissions for emergency contacts for level 4 patients), and balances security and emergency efficiency through a tiered notification mechanism.

[0051] The advantages of this technical solution are: Fine-grained access control: Through hierarchical quadratic geometric transformation and differentiated keys, patients, doctors, and contacts can access data with "least privileges" to meet the data needs of different roles; High security: It adopts geometric transformation technology of spherical coordinate mapping and ellipse cutting to avoid the complexity of traditional encryption, and prevents data leakage through key isolation and dynamic adjustment; Dynamic adaptability: Quickly adjust permissions (response time <0.5 seconds) in response to changes in the patient's condition, changes in the authorized party, etc., to ensure data availability in emergency situations; Medical Applicability: Specifically designed for the characteristics of medical data, it retains key parameters necessary for diagnosis (such as heart rate waveforms and blood pressure curves) while removing privacy markers, balancing medical applications and privacy protection; High efficiency: Geometric transformation algorithms have low computational load (e.g., the formula for spherical coordinate mapping is simple), and can be efficiently deployed in medical devices and systems without affecting real-time data processing and analysis.

[0052] The above description is merely an embodiment of the present invention and does not limit the patent scope of the present invention. Any equivalent structural or procedural transformations made based on the content of the present invention specification, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of the present invention.

Claims

1. A hierarchical medical data processing method supporting multi-party authorization, characterized in that: Includes the following steps: A basic geometric transformation is performed on the original medical data, which uses a spherical coordinate mapping method to map the original medical data into a spherical coordinate system; Assign corresponding conversion level keys to different types of authorized parties, including at least the patient, family doctor, and emergency contact, and the conversion level keys for different types of authorized parties correspond to different data access permissions; Based on the results of the basic geometric transformation, a hierarchical secondary geometric transformation is performed. Each level of secondary geometric transformation corresponds to the access rights of an licensor, and the secondary geometric transformations at different levels are independent of each other. It dynamically adjusts the hierarchical permissions of different authorized parties in response to preset trigger conditions.

2. The hierarchical medical data processing method supporting multi-party authorization as described in claim 1, characterized in that: The permissions of the conversion level key include: the patient's own key is the complete inverse conversion parameter, which can restore all the original medical data; The family doctor's key can only decipher the critical parameters used for diagnosis; The emergency contact's key can only decipher the abnormal status identifier.

3. The hierarchical medical data processing method supporting multi-party authorization as described in claim 1, characterized in that: The hierarchical quadratic geometric transformation includes elliptical cutting of the spherical coordinate mapping result, and defining the data range accessible to different authorized parties by pre-set elliptical parameters.

4. The hierarchical medical data processing method supporting multi-party authorization as described in claim 2, characterized in that: The key parameters used for diagnosis include physiological signal waveforms with privacy markers removed, which include at least one or more of heart rate waveforms and respiratory waveforms.

5. A hierarchical medical data processing method supporting multi-party authorization according to claim 2, characterized in that: The abnormal status identifier includes a Boolean status value obtained from the analysis of the original medical data. The Boolean status value is used to identify at least one or more of "abnormal heart rate" and "abnormal blood pressure".

6. The hierarchical medical data processing method supporting multi-party authorization according to claim 1, characterized in that: The preset triggering conditions include at least one of the following: changes in the patient's condition level, changes in the family doctor's identity, and adjustments to the emergency contact list.

7. A hierarchical geometric transformation system supporting multi-party authorization, characterized in that: include: The basic transformation module is configured to perform basic geometric transformations on the original medical data using spherical coordinate mapping and output the spherical coordinate mapping results. The key allocation module is configured to allocate corresponding conversion level keys to different types of authorized parties. The authorized parties include at least the patient, family doctor, and emergency contact, and the conversion level keys of different types of authorized parties correspond to different data access permissions. The hierarchical transformation module is configured to perform hierarchical quadratic geometric transformations based on the spherical coordinate mapping results. Each level of quadratic geometric transformation corresponds to the access permissions of an authorized party, and the transformation parameters of each level are isolated from each other. The permission adjustment module is configured to dynamically update the hierarchical permissions of different authorized parties and the corresponding conversion level keys based on preset trigger conditions.

8. A hierarchical medical data processing method supporting multi-party authorization according to claim 7, characterized in that: The conversion-level key permissions assigned by the key allocation module include: The patient's own key is a complete inverse transformation parameter, which can restore all the original medical data through inverse operation; The family doctor's key is associated with the decryption algorithm for key parameters used in diagnosis; The emergency contact's key is associated with the decryption algorithm for the abnormal status identifier.

9. A hierarchical medical data processing method supporting multi-party authorization according to claim 7, characterized in that: The hierarchical transformation module performs hierarchical secondary geometric transformations, including elliptical cutting of the spherical coordinate mapping results, and defines the data access range of different levels by adjusting the semi-axis length and rotation angle parameters of the ellipse.

10. A hierarchical medical data processing method supporting multi-party authorization according to claim 7, characterized in that: The preset trigger conditions for the permission adjustment module include at least one of the following: a patient's condition worsens or improves, the family doctor contract relationship changes, or the emergency contact's authorization period expires.

Images