The European Committee for Standardization ( CEN ) Standard Architecture for Healthcare Information Systems (ENV 12967), Health Informatics Service Architecture or HISA is a standard that provides guidance on the development of modular open information technology (IT) systems in the healthcare sector. Broadly, architecture standards outline frameworks which can be used in the development of consistent, coherent applications, databases and workstations. This is done through the definition of hardware and software construction requirements and outlining of protocols for communications. The HISA standard provides a formal standard for a service-oriented architecture (SOA), specific for the requirements of health services, based on the principles of Open Distributed Processing . The HISA standard evolved from previous work on healthcare information systems architecture commenced by Reseau d’Information et de Communication Hospitalier Europeen (RICHE) in 1989, and subsequently built upon by a number of organizations across Europe.
15-529: HISA may refer to: Health Informatics Service Architecture , a European Committee of Standardization protocol on IT in healthcare Horseracing Integrity and Safety Authority , a self-regulatory horse racing governance body in the United States See also [ edit ] Hisa (disambiguation) Topics referred to by the same term [REDACTED] This disambiguation page lists articles associated with
30-497: A proprietary connector design that may require a license fee from the manufacturer, or enhancements may only be installable by technicians with specialized tools or training. Computer platforms may include systems with both open and closed architectures. The Mac mini and Compact Macintosh are closed; the Macintosh II and Power Mac G5 are open. Most desktop PCs are open architecture. Similarly, an open software architecture
45-540: A standard structure that can be modified or extended per agreements between the computer systems. An example is IBM's Distributed Data Management Architecture . Open architecture allows potential users to see inside all or parts of the architecture without any proprietary constraints. Typically, an open architecture publishes all or parts of its architecture that the developer or integrator wants to share. The open business processes involved with an open architecture may require some license agreements between entities sharing
60-435: Is one in which additional software modules can be added to the basic framework provided by the architecture. Open APIs (Application Programming Interfaces) to major software products are the way in which the basic functionality of such products can be modified or extended. The Google APIs are examples. A second type of open software architecture consists of the messages that can flow between computer systems. These messages have
75-571: The Apple IIc computer has a closed architecture . Open architecture systems may use a standardized system bus such as S-100 , PCI or ISA or they may incorporate a proprietary bus standard such as that used on the Apple II , with up to a dozen slots that allow multiple hardware manufacturers to produce add-ons, and for the user to freely install them. By contrast, closed architectures, if they are expandable at all, have one or two "expansion ports" using
90-636: The HISA, these common services are divided into Healthcare-related Common Services and Generic Common Services. Healthcare-related Common Services (HCS) Healthcare-related Common Services are those middleware components responsible for supporting the functionalities and information relevant to the healthcare business domain, including subject of care, activities, resources, authorization, health characteristics and concepts. Generic Common Services (GCS) Generic Common Services are those middleware components are those middleware components responsible for supporting
105-404: The fundamental characteristics of the computational model to be implemented by the middleware, to provide a comprehensive and integrated interface to the common, fundamental business processes of the health service. The computational model, like the information model is designed to be universally relevant, whilst still being sufficiently specific to allow implementers to derive an efficient design of
120-548: The generic functionality and information requirements that are non-specific to the healthcare domain, and may be broadly relevant to any information system in the business domain. Open architecture Open architecture is a type of computer architecture or software architecture intended to make adding, upgrading, and swapping components with other computers easy. For example, the IBM PC , Amiga 2000 and Apple IIe have an open architecture supporting plug-in cards, whereas
135-405: The integration of existing information systems, within the one enterprise and across different healthcare organizations. Part one of the standard sets forth the common enterprise-level requirements (e.g. workflows, authorizations) that must be supported through the HISA, which integrates the common data and business logic into a specific architectural layer (i.e. the middleware), accessible throughout
150-1023: The specifications that became the HISA standard. Working Group I worked with experts from across Europe, plus contributors from Australia and the United States in the development and finalization of ENV 12967. The CEN HISA standard was adopted by the International Organization for Standardization (ISO) in 2009, with the stated aim of ISO 12967 being to provide guidance on: EN/ISO 12967 is broken down into three parts: Enterprise Viewpoint; Information Viewpoint; and Computational Viewpoint, all of which deal with different aspects of ensuring service architecture supports openness and vendor-independence. Part One: Enterprise Viewpoint The Enterprise Viewpoint component of EN/ISO 12967 provides health services with guidance in describing, planning and developing new IT systems, utilizing an open distributed processing approach. In addition to this it provides direction for
165-457: The system for their organisation, irrespective of the specifics of the pre-existing information technology environment in which it will be implemented. The implementation of a modular, open architecture in healthcare IT systems (as specified by the HISA) relies upon disparate heterogeneous applications interacting and communicating through a middleware layer, made up of common services. In the case of
SECTION 10
#1733114140142180-482: The system for their organisation. This specification does not aim to provide a fixed, complete specification of all possible data that may be necessary for any given health service. It specifies only a set of characteristics, in terms of overall organisation and individual information objects, identified as fundamental and common to all healthcare organizations. Part Three: Computational Viewpoint The Computational Viewpoint component of EN/ISO 12967 provides details on
195-484: The title HISA . If an internal link led you here, you may wish to change the link to point directly to the intended article. Retrieved from " https://en.wikipedia.org/w/index.php?title=HISA&oldid=1219658758 " Category : Disambiguation pages Hidden categories: Short description is different from Wikidata All article disambiguation pages All disambiguation pages Health Informatics Service Architecture The HISA standard
210-635: The whole information system of the health service. Part Two: Information Viewpoint The Information Viewpoint component of EN/ISO 12967 sets forth the fundamental characteristics of the information model to be implemented by the middleware to provide comprehensive, integrated storage of the common enterprise data and to support the fundamental business processes of the healthcare organisation, as defined in ISO 12967 Part One. The specifications were designed to be universally relevant, whilst being sufficiently specific to allow implementers to derive an efficient design of
225-414: Was developed by CEN Technical Committee (TC) 251, the technical committee for Health Informatics within the federation of European national standards bodies (CEN). The CEN/TC 251 was made up of four working groups, covering: information models; systems of concepts and terminology; security; and technologies for interoperable communication. Working Group I were responsible for information models and completed
#141858