The iCIMS’ approach to implementing a clinical system using the Lattice technology is based on a number of key points:

  • Agile implementation
  • Standardised methodology
  • Fast reiterative design – 100% user engagement
  • iCIMS is unique – Implementation is integral to the design process
  • NOBODY truly knows what they fully want from a system UNTIL they start using it, because then they know:
    • What they have, but don’t want
    • What they want, but don’t have

Implementation Stages

Stage 0 – High Level Analysis

If the client desires assistance in scoping the project, iCIMS has the experience of working with clinical teams to specify high-level (modular and functional) requirements to define an overall scope of work and project objectives. iCIMS does not require a detailed requirements analysis (e.g. down to the field level) in order to estimate effort or cost. Our methodology ensures that a client includes the key workflows and functionalities they are committing iCIMS to deliver without having to restrict themselves to a rigid level of detail that may hinder the emergence of the best-fit end-solution.

This stage concludes with a Scope of Work that feeds into stages 1-4.

Stage 1 – Clinical System Analysis

This is the starting point of any iCIMS Lattice system deployment.  The analysts engage with as many stakeholders as needed to fully understand the needs of the user community, systems requirements, workflows and connectivity essential to producing a system that is tailored to the needs of each individual client team.

One of the key outcomes is a set of requirements which on completion defines system handover.

The analysis is performed by highly experienced staff who understand clinical workflows and data regimes and can translate that information into viable technical solutions.

Stage 2 – System Design & Handover

iCIMS has a strong technology edge with Lattice.  The process of designing the solution automatically generates the system.  This enables a very short journey from prototype to final solution via a high number of iterative changes.  These changes are made in conjunction with client users and are primarily driven by the analysis completed in Stage 1. Once the design is completed as outlined in the outcome of the Stage 1 analysis, the system undergoes User Acceptance Testing (UAT) driven by a series of retrospective real patient records. At the conclusion of UAT, the system is “handed over” to the client to commission.

Stage 3 – Design Adaptation Grace Period

iCIMS offers a truly unique advantage with this stage.  It is only after a system is fully operational that users can see further areas for improvement.  It is for this reason that for three months from system handover, iCIMS works closely with each client to maximise fit for purpose. There is no charge to the client for changes made during the three month grace period. One recent client submitted ninety-eight change requests within this period.  The iCIMS implementation approach meant that 95% of the changes were made on average within 3 days of submission over those three months. iCIMS has a structured change management and adaptation approach including Change Request Forms (CRFs) that are completed and signed off by a single point of contact at the client end.

Stage 4 – Maintenance

At the completion of the Design Adaptation Grace Period, the standard maintenance stage begins. As well as standard maintenance procedures, such as bug fixes, product updates etc., iCIMS also allocates a block of hours as part of the maintenance pricing that the client can use as they see fit for design changes after the Design Adaptation Grace Period.  If the client requires further changes once they have exhausted their allocated block for the year, these requests are charged on a T&M basis at iCIMS’ standard rates.

Stage 5 – Progressive Development

This presents an important value-added service for the client under the iCIMS implementation approach where additional sub-user groups add their components onto the base system either as sub-module or a parallel Clinical Information System (CIS) within the same implementation.

This increases the Return on Investment (ROI) of the base system by leveraging the pre-existing infrastructure (installation) and connectivity. It also capitalises on iCIMS’ ability to share data easily between CISs/modules while retaining a single-gateway to communicate to the external ecosystem.