1、医院管理系统外文翻译
HL7 INTRODUCTION Introction 1.1 PURPOSE This document provides assistance to health care institutions, hospital information systems vendors,consultants and other support groups that are considering systems development and implementation activities in a multi-system environment using the Health Level Seven (HL7) protocol. This support guide includes the following information: A. Planning Methodology B. Design and Implementation Methodology C. Overview of HL7 Version 2.2 D. Overview of HL7 Version 2.3 E. HL7 Transaction Checklist F. HL7 Message Diagrams G. Lower Layer Protocols H. Helpful Hints I. Case Studies J. Sample Templates (RFI/RFP/Contract Points) K. Frequently Asked Questions The Support Guide represents the efforts of the HL7 Implementation Committee to develop support materials for organizations implementing or considering implementation of HL7 interfaces. Comments and suggestions regarding content or format are welcomed, and should be directed to the Implementation Committee Chairperson(s) listed at the end of the guide. Please keep in mind that both the planning and design/implementation methodologies are intended to serve as general guides to help in planning and implementing HL7 interfaces. This guide should be used in conjunction with your standard systems development methodology. This guide is also intended for use in conjunction with the HL7 interface standards specification document.The specification document is provided to all members of the HL7 organization. To join this organization and receive a registered copy of the current specification document, send a membership enrollment form and the appropriate fees to Health Level Seven. contract for these interfaces. The HL7 organization may develop a certification process or compliance testing proceres in the future. Institutions that are considering major systems development activities (e.g. comprehensive system upgrades/replacements), migration to an open systems architecture and/or integration of various clinical, financial or administrative systems with a central Hospital Information System (HIS) - and are considering HL7 as a mechanism for integrating these systems should refer to the planning component of the methodology. Institutions that have already made a decision to implement one or more HL7 interfaces in any type of an environment will also find certain information in the planning section useful, but should concentrate on the design and implementation sub-section of the implementation methodology covered in Chapter 3. HIS vendors should focus on the design and implementation sections, but may also consider reviewing the planning section as background. 1.2 HL7 BACKGROUND HL7 was founded in 1987 to develop standards for the electronic interchange of clinical, financial and administrative information among independent health care oriented computer systems; e.g., hospital information systems, clinical laboratory systems, enterprise systems and pharmacy systems. In the last three years, HL7’s membership has grown to exceed 1,700 hospital, professional society, health care instry, and indivial members including almost all of the major health care systems consultants and vendors. The HL7 Standard is supported by most system vendors and used in the majority of large U.S.hospitals today. It is also used internationally in such countries as Australia, Austria, Belgium, Finland,Germany, Holland, Israel, Japan, New Zealand, the Netherlands and the United Kingdom. In June of 1994, HL7 was designated by the American National Standards Institute (ANSI) as an ANSI accredited standards developer. HL7 released its fourth version of the standard (Version 2.2 ) in December 1994. This consensus standard was balloted under ANSI rules and was approved as an ANSI Standard on February 8, 1996. Version 2.3, which was released on CD-ROM in April of 1997, was approved as an ANSI Standard on May 13, 1997. 1.3 HL7 TRANSACTIONS The Version 2.3 Standard defines transactions for transmitting data about patient registration, admission,discharge and transfers, insurance, charges and payors, orders and results for laboratory tests, image studies,nursing and physician observations, diet orders, pharmacy orders, supply orders, master files, appointment scheling, problem lists, clinical trial enrollments, patient permissions, voice dictations, advanced directives, and physiologic signals. Task forces in HL7 are also busy developing prototype transactions with new state of the art technologies such as CORBA and Microsoft’s OLE objects. 1.4 COOPERATION WITH OTHER STANDARDS DEVELOPING ORGANIZATIONS HL7 has a pure focus on health care informatics standards and cooperates closely with other standards developers such as American Society for Testing and Materials (ASTM), Accredited Standards Committee X12N, American College of Radiology (ACR), National Electrical Manufacturers Association (NEMA),National Council for Prescription Drug Programs (NCPDP), and Institute of Electronics and Electrical1.5 OVERVIEW This section is an excerpt from Chapter 1 of the HL7 Version 2.3 Standard and contains a description of the conceptual basis of the HL7 Standard, the approach to accommodating intra-site variations and evolutionary changes, and the way it has been structured in order to accommodate varying current and future communications environments. 1.5.1 HL7 Encoding Rules Message formats prescribed in the HL7 encoding rules consist of data fields that are of variable length and separated by a field separator character. Rules describe how the various data types are encoded within a field and when an indivial field may be repeated. The data fields are combined into logical groupings called segments. Segments are separated by segment separator characters. Each segment begins with a three-character literal value that identifies it within a message. Segments may be defined as required or optional and may be permitted to repeat. Indivial data fields are found in the message by their position within their associated segments. All data is represented as displayable characters from a selected character set. The ASCII displayable character set (hexadecimal values between 20 and 7E, inclusive) is the default character set unless modified in the MSH header segment. All the other special separators and other special characters are also displayable characters, except that the segment separator is the ASCII Carriage Return character. 1. There is nothing intrinsic to HL7 Version 2.3 or ASTM 1238 that restricts the legal data set to the printable ASCII characters. The former restriction was imposed to accommodate the limitations of many existing communication systems. Some existing systems would misinterpret some eight-bit characters as flow control characters instead of data. Others would strip off the eighth bit. 2. The European community (EC) has a need for printable characters (for example, the Germanoe, the French accent grave) that are not within the above-defined restricted data set. The personal computer market accommodates these alphabetic characters by assigning them to codes between 128 and 256, but it does this in many different ways. ISO 8859 is a 256-character set that does include all of the needed European letters and is a candidate for the European standards group. Where the Europeans define an eight-bit character set specification, HL7 will accept this data set in environments that require it, and can use it without complications. 3. Multi-character Codes: a. UNICODE - When communicants use UNICODE, and all characters are represented by the same number of bytes, all delimiters will be single characters of the specified byte length, and the Standard applies just as it does for single-byte length, except that the length of the characters may be greater than one byte. b. JIS X 0202 - ISO 2022 provides an escape sequence for switching among different character sets and among single-byte and multi-byte character representations. Japan has adopted ISO 2022 and its escape sequences as JIS X 0202 in order to mix Kanji and ASCII characters in the same message. Both the single- and multiple-byte characters use only the low order 7 bits in JIS Kanji code with JIS X 0202 in order to ensure transparency over all standard communication systems. When HL7 messages are sent as JIS X 0202, all HL7 delimiters must be sent as single-byte ASCII characters, and the escape sequence from ASCII to Kanji and back again must occur within delimiters. In most cases the use of Kanji will be restricted to text fields.There are other parts of the JIS X series that support Katakana (JIS X 0201/ISO IR 13),Romaji (JIS X 0201/ISO IR 14) and Kanji (JIS X 0208/ISO IR 87) and (JIS X 0212/ISO IR 159) that can be used in HL7 messages in the same manner as JIS X 0202. c. In the case that a single country uses conflicting rules for representing multi-byte The encoding rules distinguish between data fields that have the null value and those that are not present. The former are represented by two adjacent quotation marks, the latter by no data at all(i.e., two consecutive separator characters.) The distinction between null values and those that are not present is important when a record is being updated. In the former case the field in the database should be set to null; in the latter case it should retain its prior value. The encoding rules specify that if a receiving application cannot deal with a data field not being present, it should treat the data field as present but null.The encoding rules specify that a receiving application should ignore fields that are present in the message but were not expected rather than treat such a circumstance as an error.
2、车辆管理系统毕业论文。怎么办呢？
?
3、求一篇人事管理系统的外文翻译
童鞋你好！
这个估计需要自己搜索了！
网上基本很难找到免费给你服务的！
就算别人给你找的，也未必能满足你的需要！
并且，找资料在以后的工作中是必备的技能之一啊！
所以，我在这里给你点搜索国际上常用的外文资料数据库：
----------------------------------------------------------
⑴ISI web of knowledge Engineering Village2
⑵Elsevier SDOL数据库 IEEE/IEE(IEL)
⑶EBSCOhost RSC英国皇家化学学会
⑷ACM美国计算机学会 ASCE美国土木工程师学会
⑸Springer电子期刊 WorldSciNet电子期刊全文库
⑹Nature周刊 NetLibrary电子图书
⑺ProQuest学位论文全文数据库
⑻国道外文专题数据库 CALIS西文期刊目次数据库
⑼推荐使用ISI web of knowledge Engineering Village2
-----------------------------------------------------------
如果你真的不愿意自己找的话，那就进行追问吧！
中文翻译得自己做了，实在不成就谷歌翻译。
弄完之后，自己阅读几遍弄顺了就成啦！
学校以及老师都不会看这个东西的！
外文翻译不是论文的主要内容！
所以，很容易过去的！
祝你好运！
4、求关于毕业设计管理系统的外文文献及翻译！
是要英文和中文互译的那种吧