Chapter 2.pptx

Chapter 2: The Building Blocks of Health & Informatics Chapter 2  Health Information Interchange  Modelling Healthcare Information  Introduction to Database  Knowledge Management Health Information Interchange  Health Information Exchange (HIE) is the mobilization of heal...

Chapter 2: The Building Blocks of Health & Informatics Chapter 2  Health Information Interchange  Modelling Healthcare Information  Introduction to Database  Knowledge Management Health Information Interchange  Health Information Exchange (HIE) is the mobilization of health care information electronically across organizations within a region, community or hospital system.  In practice the term HIE may also refer to the organization that facilitates the exchange.  HIE provides the capability to electronically move clinical information among different health care information systems  Health information interchange GOALS of HIE  The goal of HIE is to facilitate access to and retrieval of clinical data to provide safer and more timely, efficient, effective, and equitable patient-centered care.  HIE systems facilitate the efforts of physicians and clinicians to meet high standards of patient care through electronic participation in a patient's continuity of care with multiple providers.  Health Information Interchange Secondary health care provider benefits include reduced expenses associated with:  the manual printing, scanning and faxing of documents, including paper and ink costs, as well as the maintenance of associated office machinery  the physical mailing of patient charts and records, and phone communication to verify delivery of traditional communications, referrals, and test results  the time and effort involved in recovering missing patient information, including any duplicate tests required to recover such information  Health information interchange  Healthcare organization - collaborate in the pursuit of solutions to healthcare information management issues  Includes standards for data interchange, clinical vocabularies, services, security, document architectures etc Leading healthcare data interchange standards Introduction to Database What is database  Database: A collection of data and information describing items of interest to an organization  Database Management System (DBMS): A program that makes it possible for users to manage the data in a database in order to increase accessibility and productivity Database Systems  A database system  Database systems allow users consists of to  Data (the database)  Store  Software  Update  Hardware  Retrieve  Users  Organise   Protect We focus mainly on the software their data. Why Study Databases?  Databases are useful  Databases in CS  Many computing applications  Databases are a ‘core topic’ in deal with large amounts of computer science information  Basic concepts and skills with  Database systems give a set of database systems are part of the tools for storing, searching and skill set you will be assumed to managing this information have as a CS graduate Examples of Database Applications  Purchases from the supermarket  Purchases using your credit card  Booking a holiday at the travel agents  Using the local library  Taking out insurance  Renting a video  Using the Internet  Studying at university File-Based Systems  Collection of application programs that perform services for the end users (e.g. reports).  Each program defines and manages its own data. File-Based Processing Limitations of File-Based Approach  Separation and isolation of data  Each program maintains its own set of data.  Users of one program may be unaware of potentially useful data held by other programs.  Duplication of data  Same data is held by different programs.  Wasted space and potentially different values and/or different formats for the same item. Limitations of File-Based Approach  Data dependence  File structure is defined in the program code.  Incompatible file formats  Programs are written in different languages, and so cannot easily access each other’s files.  Fixed Queries/Proliferation of application programs  Programs are written to satisfy particular functions.  Any new requirement needs a new program. Database Approach  Arose because:  Definitionof data was embedded in application programs, rather than being stored separately and independently.  No control over access and manipulation of data beyond that imposed by application programs.  Result:  the database and Database Management System (DBMS). Database  Shared collection of logically related data (and a description of this data), designed to meet the information needs of an organization.  System catalog (metadata) provides description of data to enable program– data independence.  Logically related data comprises entities, attributes, and relationships of an organization’s information. Database Management System (DBMS)  A software system that enables users to define, create, maintain, and control access to the database.  (Database) application program: a computer program that interacts with database by issuing an appropriate request (SQL statement) to the DBMS. Database Management System (DBMS) Advantages of DBMSs  Control of data redundancy  Data consistency  More information from the same amount of data  Sharing of data  Improved data integrity  Improved security  Enforcement of standards  Economy of scale Introduction to database-ANSI/SPARC three-tier DBMS architecture Introduction to database-ANSI/SPARC three-tier DBMS architecture External/user view level Multiple user views (staff and health service consumers) E.g. Physician view clinical data different from nurse or physiotherapist Conceptual Schema Logical view of entire database as unified as whole (from all user view) Data Definition Language (DDL) - technology independent not dependent on physical storage and data access details Internal/physical schema Internal physical database structure Information about stored files/relations Structure of stored database is changed then Modelling healthcare information  1. Entity-relationship (E-R) -difficult for relationship entities at national level  2. Unified Modelling Language (UML) _assist in comprehending the Health Level 7 (HL7)  3. Object-Role Modelling (ORM) notations E-R model Entity type  Group of objects with same properties, identified by enterprise as having an independent existence. Entity occurrence  Uniquely identifiable object of an entity type. Relationship type  Set of meaningful associations among entity types. Relationship occurrence  Uniquely identifiable association, which includes one occurrence from each participating entity type.  In UML - relationships between things is a key function. Four types of relationships: dependency, association, generalisation and realisation  Dependency: relationship where a change to one object changes the meaning of something else. It is illustrated in models using a dahsed line  Association: Link connecting between two objects. It is illustrated by sound line Object Role Modeling  Object Role Modeling (ORM) is a powerful method for designing and querying database models at the conceptual level, where the application is described in terms easily understood by non-technical users. Knowledge management  Knowledge is the body of understanding and skills that are mentally constructed by people. It synthesised information with interrelationships identified and formalised  Thinking process comprise a theortical component that is well documented, but applied component derived from practice. Knowledge management  Knowledge management as four-part loop process  1.Creation and elicitation  2.Capture and storage  3.Dissemination  4.Application and exploitation Ref  http://vlib.moh.gov.my/cms/index.jsp?id=com.tms.cms.bookmark.Bookmark_Home  www.youtube.com