Understand the existing portal
Shinetech engineers examined the application’s functions and framework before implementing changes. They also adjusted the login workflow to present a password-change form when a password had expired.
Case study · Healthcare
A US healthcare provider extended its clinical information portal with tools for creating subsites, distributing documents and recording list actions.

The situation
The provider already used SharePoint as an information centre for healthcare practitioners. It wanted additional functions that made the existing environment easier to manage and clinical information easier to distribute.
The requested Web Parts needed to work with the original architecture and the SharePoint object model. They covered creating subsites, pushing documents from parent sites and recording actions on site lists.
The approach
Shinetech engineers examined the application’s functions and framework before implementing changes. They also adjusted the login workflow to present a password-change form when a password had expired.
An Enroll Site Web Part allowed users to create a subsite for the current site and choose from available templates.
The Push Documents Web Part used a tree representation of the site organisation. Users could select libraries, folders, documents and target subsites for distribution.
Project context
Technologies and working practices used in this engagement.
The result
Custom Web Parts added the requested site-management functions to the clinical information environment.
The tree-based selection supported multiple documents and subsites within the distribution workflow.
The project used C#, ASP.NET, IIS 6, SharePoint Services and SQL Server on Windows Server 2003.
Tell us about your software, workflows and delivery requirements.
Discuss your project