Project: HL7 Data transcription

1
Welcome!

• Project HL-7 Data transcription
• Name of our Group
• UOB Project Group2006
• uob_project2006_at_yahoo.com.au

2
Team Members

• Hemal Karambelkar Project Manager
• Rushit Shah Senior Programmer
• Babu Chaudhary Junior Programmer
• Ketan Soni DBA

3
Organizational Chart
4
Introduction

• The main goal is to
• Design a window application
• Which will convert HL-7 data into to image
  segments.
• These image segments are called as Train Diagram.
• Also, the image should be converted back into the
  data.

5
Sponsors

• University of Ballarat is sponsoring the project.
• Client
• It is Mr. Chris Lynton.
• He is Executive director of Collaborative Care
  Communications

6
Time Span

• Starting Date 22/03/2006
• Duration Around 80 days
• Ending Estimated to end in mid June.

7
Cost Management

• FREE!
• University of Ballarat is providing the
  resources.
• Purpose is academic.
• Estimated cost is 45K

8
About HL7

• The Protocol
• HL7 is a standard for information exchange
  between medical applications.
• It is an abbreviation of "Health Level Seven",
• 7th OSI layer protocol for the health
  environment.

9
In Australia

• Standards Australia Working Group IT 14-6-6
  participates in the generation of Health Level
  Seven (HL7) messaging standards.
• The versions The most popular versions at this
  time are v2.3.1 v2.4.

10
What it is ?

• It defines the format and the content of the
  messages that applications must use.
• It is used when exchanging data with one another.
  
• It defines a communication between two
  independent applications.
• Previously it was between closely coupled and
  client-server type applications.

11
Background

• A group of healthcare computer systems users (who
  later founded the Health Level 7 organization) in
  1987 started developing the HL7 protocol.
• Over time the HL7 interoperability protocol
  became a nationally, internationally and globally
  accredited standard.

12
A Data Sample

• ORMO01 ORM_O01 Usage Cardinality Description HL
  7 Chapter
• MSH R 1..1 Message Header 2
• NTE X Notes and Comments (for Header) 2
• R Segment Group Patient Details
• PID R 1..1 Patient Identification 3
• PD1 X 0..1 Additional Demographics 3
• NTE X Notes and Comments (for Patient
  ID) 2
• RE 0..1 Segment Group Patient Visit
• PV1 R 1..1 Patient Visit 3
• PV2 X 0..1 Patient Visit Additional
  Info 3
• RE 0..1 Segment Group - Insurance
• IN1 R 1..1 Insurance 6
• IN2 X Insurance Additional Info 6
• IN3 X Insurance Addl Info Cert 6
• GT1 X 0..1 Guarantor 6
• AL1 X Allergy Information 3

13
Conventions

• In the descriptive text curly brackets represent
  repeating segments.
• The square brackets represent optional segments.

14
Image
15
Conventions

• In the image, lines on top of the line of
  segments represent repeating segments
• The lines under the segments represent optional
  segments.

16
Evolution of Project Plan

• We are going to update the project plan as the
  changes are identified in the requirement of the
  client.
• Project plan will be handled by the project
  manager
• He is responsible for approving the necessary
  changes.
• Also, adding the required modifications through
  out the Software Development Life Cycle.

17
Project Deliverables

• A Software Project Management Plan Document
• Work Breakdown Structure
• Software Requirement Specification Document
• Software Design Document
• Minutes of the meeting Reports
• Weekly Status Reports
• A Final product meeting clients requirements

18
Managerial Process

• Management Objective and Priorities
• For successful project completion, the management
  gives highest priority to meet the client in
  order to be specific about the requirements.
• It can be ensured by regular meetings of the
  project team with the client thought out the
  software development life cycle.

19
Managerial Process Continued

• Assumptions, Dependencies, and Constraints
• Techniques such as dependency lists, activity
  networks, and the critical path method may be
  used to depict dependencies among work packages.

20
Technical Process

• Methods, Tools and Techniques
• Software Requirements
• Microsoft Office 2003
• Microsoft Project 2003
• Visual Studio 2003 .NET and
• Rational Rose

21
Technical Process Continued..

• Hardware Requirements
• Processor Pentium III
• Memory 256 Megabytes
• Free Hard Disk Space 256 Megabytes

22
Risk Management

• Lack of experience
• All the team members have assigned tasks
  according to their roles and experience they have
  gathered during study.
• Loss of Data
• Steps are taken to backup the data that includes
  on CDs, Floppies and USB storage devices
• Shortage of Time
• Every member will monitor the projects progress
  throughout the entire phase of the project. In
  case of delays, the schedule will be adjusted and
  the required changes will be discussed.

23
Work Packages, Schedule and Budget

• This section gives the complete work packages
  required for this project, the schedule of the
  project and the budget for the completion of the
  project.
• Work Packages
• project are divided into sub-activities and tasks
  which are included in the work breakdown
  structure
• Dependencies
• Techniques such as dependency lists, activity
  networks, and the critical path method may be
  used to depict dependencies among work packages.

24
Work Packages, Schedule and Budget (Continued)

• Resource Requirements
• Resource Requirements provide estimates of the
  total resources required to complete this
  project. This includes the total time requirement
  and the total cost estimation.
• Budget
• Specifies the allocation of budget and resources
  to the various project functions, activities, and
  tasks.
• Schedule
• gives the information about the detailed schedule
  for the various project activities and tasks,
  taking into account the precedence relations and
  the required milestone dates.

25
Monitoring and Controlling

• Weekly Status Reports
• contains the description of the status of the
  project recorded every week
• Coordinator/Supervisor Meetings
• These meetings will provide an opportunity to get
  any feed back from the project team coordinator
  as well as the supervisor.
• Team Meetings
• A major team meeting will be held on the Monday
  of every week. This meeting will be conducted to
  ensure that all required work being completed and
  to allocate any new tasks.

26
Software Requirement Specification

• Aim is to define functional and non-functional
  requirements
• That will be used for future system design and
  specification
• It will also help for testing and updating system

27
The principle scopes of this document are
mentioned as below

• It describe the scope of product which is
  undertaken by project
• It also describe the user classes and interface
  which are involved with this product.
• Describe the functionality or any
  non-functionality for this product.
• It explains the acronyms and abbreviations that
  are used.

28
System Features

• System will be developed using 2 modules
• Stage 1 It consists of parsing text that
  produce image or train diagram
• Stage 2 It consists of parsing image that
  produce meaningful text
• Database Management
• For Stage 2 we are using MySQL Database

29
Non-Functional Requirements

• Performance
• It is expected that the system would perform all
  the required functionality.
• Safety
• The database may damage at any certain time due
  to hardware scratched or operating system
  failure. Thus, the database backup and data lose
  recovery needed to be planed for this failure.

30
Current System

• Currently this work is being done by MS word or
  Visio or Smart draw.
• Text is prepared in MS Word in tabular form
• Image is produced in Visio or Smart draw.

31
About System

• HL 7 transcribe utility is used to convert the
  text from image and from image to text
• The master form

32
About System

• System Takes Input as a word document or Image
  (.Jpeg Format)
• File menu
• Save
• Discard
• Exit
• Utility menu
• Convert Text
• Convert Image (Yet to be done)

33
HL 7 Text Message

34
Train Diagram