StableVersion4.3/HL_FristAidPlatform_Apoplexy/Page/UserControl_AcuteIschemicSt...

158 lines
8.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="labelControl24.Text" xml:space="preserve">
<value>四、一、实行该手术存在的风险及可能发生的意外和并发症
1.此手术可能发生的风险、并发症和意外
⑴血管部分或全部再通,但症状无改善,甚至加重:
⑵血管无法再通,或再通后再次闭塞,症状无改善或恶化,新发梗死,危及生命;
⑶颅内出血或再灌注损伤,导致偏瘫、失语、癫痫甚至昏迷等症状,必要时转为开颅手术,甚至危及生命;
⑷术中出现颅内外血管痉挛、夹层造成动脉闭塞甚至脑梗死或是动脉破裂,出现相关症状,甚至危及生命
⑸小栓子脱落向远端血管逃逸导致再次梗塞,使已经恢复的神经功能再次缺损;
⑹血气栓、异物、动脉粥样硬化斑块等栓塞以及脑血栓形成造成脑梗死;
⑺导管、导丝、支架打折、打结甚至断裂,滞留体内难以取出,并造成脑梗死;
⑻药物过敏,发生溶血、发热、皮参、哮喘甚至过敏性休克;
⑼穿刺部位血肿、硬结、感染、腹膜后出血、假性动脉瘤及股动脉业住甚至危及生命;
⑽动脉血管严重硬化、迂曲、血管开口狭窄明显,造影导管、微导管、支架无法到位,手术无法完成,患方仍需承担相应费用;
⑾术中心脑血管疾病急性发作,导致呼吸循环衰竭;
⑿造影发现远端分支血管闭塞、微导管及支架无法到位和开通血管,症状无法改善;
⒀溶栓及抗凝药物导致其他部位出血,危及生命;
⒁DSA机器故障,检查或治疗不能如期进行或完成
⒂其他无法预料的情况。
2.手术麻醉存在的风险(详见《麻醉同意书》)。
3.拒绝手术可能导致的严重后果:病情持续加重、危及患者生命、失去手术最佳治疗时机、引起各种严重的并发症、
多脏器器官功能损害等。
4.部分手术麻醉费用及材料费为自费或部分自费。
5.任何所用药物都可能产生不良反应,包括轻度恶心、皮疹等症状,直至严重的过敏性休克,甚至危及生命。
6.对于患有高血压、心脏病、糖尿病、肝肾功能不全、静脉血栓等疾病,或者有吸烟、酗酒史的患者,
以上这些风险可能会加大,或者在术中或术后出现相关的病情加重或心脑血管意外,甚至死亡。
7.如患者术后不遵医嘱或不配合治疗,可能影响手术效果。
8.其他难以预料的,危及患者生命等意外情况。</value>
</data>
<data name="labelControl14.Text" xml:space="preserve">
<value>五、替代治疗方案告知
保守治疗或单纯静脉溶栓治疗:症状无改善甚至持续恶化。
我们对以上各项均已了解清楚,同意接受手术治疗,愿意承担因此而带来的各种风险。
并同意:
1.手术中发现的情况可能与术前估计有差异,在手术操作中医师可以根据患者的病情征得法定代理人签字同意后,
对预定的操作作出调整。
2.授权医师对于操作切除的病变器官、组织或者标本进行处置,包括病理学检查、细胞学检查和医疗废物处理等。
</value>
</data>
</root>