StableVersion4.3/HL_FristAidPlatform_Apoplexy/Page/UserControl_IntracranialAne...

147 lines
7.6 KiB
XML

<?xml version="1.0" encoding="utf-8"?>
<root>
<!--
Microsoft ResX Schema
Version 2.0
The primary goals of this format is to allow a simple XML format
that is mostly human readable. The generation and parsing of the
various data types are done through the TypeConverter classes
associated with the data types.
Example:
... ado.net/XML headers & schema ...
<resheader name="resmimetype">text/microsoft-resx</resheader>
<resheader name="version">2.0</resheader>
<resheader name="reader">System.Resources.ResXResourceReader, System.Windows.Forms, ...</resheader>
<resheader name="writer">System.Resources.ResXResourceWriter, System.Windows.Forms, ...</resheader>
<data name="Name1"><value>this is my long string</value><comment>this is a comment</comment></data>
<data name="Color1" type="System.Drawing.Color, System.Drawing">Blue</data>
<data name="Bitmap1" mimetype="application/x-microsoft.net.object.binary.base64">
<value>[base64 mime encoded serialized .NET Framework object]</value>
</data>
<data name="Icon1" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64">
<value>[base64 mime encoded string representing a byte array form of the .NET Framework object]</value>
<comment>This is a comment</comment>
</data>
There are any number of "resheader" rows that contain simple
name/value pairs.
Each data row contains a name, and value. The row also contains a
type or mimetype. Type corresponds to a .NET class that support
text/value conversion through the TypeConverter architecture.
Classes that don't support this are serialized and stored with the
mimetype set.
The mimetype is used for serialized objects, and tells the
ResXResourceReader how to depersist the object. This is currently not
extensible. For a given mimetype the value must be set accordingly:
Note - application/x-microsoft.net.object.binary.base64 is the format
that the ResXResourceWriter will generate, however the reader can
read any of the formats listed below.
mimetype: application/x-microsoft.net.object.binary.base64
value : The object must be serialized with
: System.Runtime.Serialization.Formatters.Binary.BinaryFormatter
: and then encoded with base64 encoding.
mimetype: application/x-microsoft.net.object.soap.base64
value : The object must be serialized with
: System.Runtime.Serialization.Formatters.Soap.SoapFormatter
: and then encoded with base64 encoding.
mimetype: application/x-microsoft.net.object.bytearray.base64
value : The object must be serialized into a byte array
: using a System.ComponentModel.TypeConverter
: and then encoded with base64 encoding.
-->
<xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
<xsd:import namespace="http://www.w3.org/XML/1998/namespace" />
<xsd:element name="root" msdata:IsDataSet="true">
<xsd:complexType>
<xsd:choice maxOccurs="unbounded">
<xsd:element name="metadata">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="value" type="xsd:string" minOccurs="0" />
</xsd:sequence>
<xsd:attribute name="name" use="required" type="xsd:string" />
<xsd:attribute name="type" type="xsd:string" />
<xsd:attribute name="mimetype" type="xsd:string" />
<xsd:attribute ref="xml:space" />
</xsd:complexType>
</xsd:element>
<xsd:element name="assembly">
<xsd:complexType>
<xsd:attribute name="alias" type="xsd:string" />
<xsd:attribute name="name" type="xsd:string" />
</xsd:complexType>
</xsd:element>
<xsd:element name="data">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
<xsd:element name="comment" type="xsd:string" minOccurs="0" msdata:Ordinal="2" />
</xsd:sequence>
<xsd:attribute name="name" type="xsd:string" use="required" msdata:Ordinal="1" />
<xsd:attribute name="type" type="xsd:string" msdata:Ordinal="3" />
<xsd:attribute name="mimetype" type="xsd:string" msdata:Ordinal="4" />
<xsd:attribute ref="xml:space" />
</xsd:complexType>
</xsd:element>
<xsd:element name="resheader">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
</xsd:sequence>
<xsd:attribute name="name" type="xsd:string" use="required" />
</xsd:complexType>
</xsd:element>
</xsd:choice>
</xsd:complexType>
</xsd:element>
</xsd:schema>
<resheader name="resmimetype">
<value>text/microsoft-resx</value>
</resheader>
<resheader name="version">
<value>2.0</value>
</resheader>
<resheader name="reader">
<value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
</resheader>
<resheader name="writer">
<value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
</resheader>
<data name="labelControl10.Text" xml:space="preserve">
<value>三、实行该手术存在的风险及可能发生的意外和并发症
1.造影术中或术后可能出现的问题:
①造影剂过敏致过敏性休克,危及生命;
②操作及造影部位血管损伤、出血及远端血管栓塞、破裂出血;
③肝肾功能衰竭。
2.介入治疗手术可能出现的问题:
① 在患者搬运、麻醉及准备过程中,可能出现动脉瘤或血管畸形破裂出血,加重病情甚全危及生命;
② 因使用肝素等抗凝药物,造成凝血机制障碍,可能出现多系统出血性疾病;
③介入器材在血管内可诱发血栓,造成脑及其他脏器栓塞;
④操作部位及相关部位的血管痉挛、栓塞、夹层或出血造成相应组织功能缺失,甚至生命危险;
⑤栓塞物(弹簧圈、胶、球囊等)移位、早脱造成功能血管的闭塞,甚至生命危险;
⑥动脉瘤颈再生长,破裂出血;
⑦因血流动力学改变,造成出血或缺血,严重者可造成残疾或死亡。
3.造影及介入治疗手术均有可能不成功,中途终止;出现意外后,可能转为开预手术治疗。
4.造影有3-5‰、介入治疗有5%左右的病人有生命危险。
5.在现有科学技术条件下,无法预料或者不能防范的不良后果。
6.手术中出现紧急情况时,医师可先行处理。
7.若发生并发症,由此产生的抢救及治疗费用应由患者方承担。
(二)手术麻醉存在的风险(详见《麻醉同意书》)。
(三)任何所用药物都可能产生不良反应,包括轻度恶心、皮疹等症状,直至严重的过敏性休克,甚至危及生命。
(四)对于患有高血压、心脏病、糖尿病、肝肾功能不全、静脉血栓等疾病,或者有吸烟、酗酒史的患者,以上这些风险
可能会加大, 或者在术中或术后出现相关的病情加重或心脑血管意外,甚至死亡。
(五)如患者术后不遵医嘱或不配合治疗,可能影响手术效果。
(六)其他难以预料的,危及患者生命等意外情况。
</value>
</data>
</root>