Forms for each instrument
Collect the sample details and analysis choices required for each instrument.
← All case studies
Scientific research · Facility operations
From laboratory request to result, in one place
For a major Government of India scientific research organisation, we connected the steps of requesting laboratory analysis: finding an instrument, submitting details, getting approval, scheduling work, and receiving results.
The challenge
Different instruments need different details.
Requesting a laboratory analysis involves more than booking a time. People need to find the right instrument, choose the analysis, and provide the sample details that specialists need.
Facility teams then check each request, approve or reject it, schedule the work, record costs, and share results. Different instruments and services need different questions, so one standard form is not enough.
Clear responsibilities
Help requesters, project leaders, reviewers, specialists, and administrators make and track decisions.
A clear view of the work
Bring schedules, sample status, downtime, costs, documents, and reports into one place.
The solution
Connected tools for requesters and facility staff.
Arctech built two connected ASP.NET Core applications. External requesters can register, find instruments, complete the relevant forms, and manage their orders. They can also access documents, request support, and provide feedback.
Facility staff use a separate application to review requests, schedule work, manage costs and transactions, and upload results. Email updates cover registration, decisions, schedule changes, proforma documents, completion, support, and feedback.
Instrument discovery
Help people find the right facility, instrument, and analysis before they submit a request.
Forms that fit the request
Use more than 60 instrument-specific form templates to collect the scientific details each service needs.
Facility operations
Give staff tools to review work, manage schedules and costs, share results, and prepare reports.
Architecture
Two applications working together.
Both applications use server-rendered pages and shared services to handle forms and decisions. SQL Server stores the information that connects requests with the facility team’s work.
Requester applicationDiscovery, requisitions, orders and documents
Workflow servicesFacilities, instruments, users and decisions
SQL ServerOperational data and stored procedures
Operations applicationReview, scheduling, costs and results
OutputsPDFs, notifications and reporting
Delivery approach
Improving as laboratory needs change.
The platform has grown through focused improvements to instrument forms, permissions, requests, emails, schedules, logbooks, reports, and document exports.
The code separates business rules and data access, with validation and settings for development, staging, and production. This case study describes verified functionality; delivery methods, automated releases, and measured business results are not covered.
Connected workflowFollow each request from finding an instrument to receiving results.
Adaptable data captureCollect the details each instrument needs through tailored forms.
Workflow communicationKeep people informed about registration, decisions, schedule changes, and completion.
A clear view of the workHelp staff review schedules, samples, status, logbooks, and equipment use.
.NET 7ASP.NET CoreRazor PagesEntity Framework CoreSQL ServerASP.NET Core IdentityAutoMapperSerilogPDF generation
Need an easier way to manage specialist service requests?
Talk to our team →This is one of several platforms delivered for the same unnamed research organisation. Read the research portal case study.