Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

OSHIP Features: 

Implemented
Internationalization/localization - OSHIP comes ready to go for translations using standard 'gettools' applications.  Collaborative translations are already underway in Brazilian Portuguese, Spanish, German, Korean, Japanese and Dutch at the Launchpad home of OSHIP.

Workflow Management Coalition compliant engine -WfMC is the standard for workflow engines.

Complete object event triggers - Object events are triggered on every, create, copy, move, change and delete action; application wide.

 Transparent Persistence - OSHIP objects are transparently persisted in a robust, transactional object database with ACID functionality.  This reduces code usage compared with ORM by 30% or more.  Interfaces do exist for all major SQL databases if the user has that need.

 openEHR Reference Model - OSHIP uses the openEHR reference model for information management plus the openEHR archetype model to express constraints. (80% complete)

Dublin Core - OSHIP objects add the capability to use standardized Dublin Core meta-data for enhanced application richness.

HTML/XML Templating - Robust XML processing producing standards compliant HTML pages.

Form Generation and Validation - OSHIP can automatically produce forms and validate input based on definitions in the class interfaces.

Security - OSHIPs security model can provide access permissions/restrictions at an attribute level.

Indexing/cataloging - OSHIP comes with a built-in, proven indexing and cataloging system providing attribute level as well as free text cataloging.

Testing - The complete OSHIP package comes with more than 5000 (and growing) automated tests.

Scalability - The underlying architecture of OSHIP is proven in daily use to be scalable to billions of objects with thousands of concurrent users.

Open Source - OSHIP, from top to bottom is open source and cross-platform implementable.

Planned

openEHR Template Persistence and processing - Storage and processing of reusable openEHR templates.

Archetype Query Language - Editor and persistence for reusable, standardized queries.

Decision Support - The CLIPS inference engine is one of the most proven and best known engines available.  Wrapped with the Python API (PyCLIPS)  the engine will initially be integrated to process First Order Predicate Logic (FOPL) embedded in archetypes.  In the second phase CLIPS will be used (in a similar fashion to the design I did for EGADSS) to use HL7v3 messages as well as AQL queries.

  • No labels