Openapp.ie Application Integration Services

Below are listed a number of systems architectures we OpenApp have implemented which demonstrate our skills and experience in integrating disparate products and technologies.

Email and Groupware Solution

The objective was th build an  IT Architecture to integrate eMail, Messaging, Calendar and Contact Information, building on existing systems while enabling the widest choice of current and future clients - MS Outlook, Open Source Groupware Clients, Commodity Mobile Devices, Internet Browsers – with sychnonising Push and Pull capability.

Primary Services

1. Email
2. Calendaring
3. Address Books
4. Task Management
5. Portal Services - Document Collaboration – Web Applications - Communications
6. File Management

Clients Supported

1. Browser – MS Internet Explorer, Firefox
2. MS Outlook (limitations on older versions) and MS Outlook Express (mail only)
3. Mobile Device – all devices supporting SyncML Standard including commodity Nokia and Motorola and other phones, Blackberry, iPaq and other WinCE devices.
4. OSS Groupware Clients – Evolution, Thunderbird, Sunbird, Kmail etc.
5. Windows Explorer for File Management
6. 6Other File Management clients – Konqueror or Finder(Mac) or similar

Document Management at Beaumont Hospital Dublin

Beaumont Hospital DMS – Document Management System

The DMS currently incorporates document managememnt features that can support (maybe with minor modifications) the needs of Accreditation to a Health Service Quality Standard

The system to manage documents which addresses the following

1. Authoring – the ability to create either by individuals or groups.
2. Review – the ability to review, comment, accept, reject – the ensure qualified persons approve documents for use.
3. Publish - the ability to make available for use – to ensure the correct version in in use
4. Archive – the ability to save and access older copies, maybe under controlled access
5. Access – the ability to make the document available to all who might need it – wherever they might need it.
6. Revision Control – the ability to manage changes
7. Roles, identification and security – to ensure that only the right people can take actions in the right place
8. Reports (views on screen) – the ability to list documents to a given criteria e.g. All expired documents
9. Roles
   • Author – anyone who can create or edit a document
   • Department Reviewer – local review – usually for content correctness
   • Document Manager – review for document correctness – format meets requirements
10. Document Formats
• All Microsoft and StarOffice formats are supported for editing
• Documents could be published in Adobe PDF format only (to prevent accidental editing)
• Reports or Views
  • Multiple
  • Collections of Documents
11. There are a number of mechanisms that can be used to group documents
• Keywords – set on the properties page – should be controlled
• Place – where they were created – where they are published
• Book, Chapter, Page – can be used to create an equivalent of a real book using files (A Microsoft Word document for instance) as the page.
12. Default Workflow

DMS incorporates a default publishing workflow – maybe not all elements are necessary or appropriate in all cases.

• Edit Online has proved problematic due to various PC setups – it could maybe be used by 'named' authors but turned off for others. (Create an Author Role to identify these).
• Check-Out, Check-In – can be a little confusing, but works well when used properly – useful if a number of people can potentially edit the same document.
• Read and Acknowledged – useful if we want acknowledgement that people know of the existance of a new document or revision – must be 'logged-in' to use (so we know the name)
• Submit to multiple sections – useful for restricted access documents where 'Local Roles' are set on s folder.