How eQMS implementation works, in three steps
About eight weeks is typical. What varies is what your product and your markets require, which is what the first step establishes.
The three steps
Map it, build it, validate it
Map it.
We work through five things with you. Your target markets, whether that is the United States, Europe, or both. Your product type: sterilized, implanted, IVD, diagnostic. Whether you manufacture in house or by contract. Whether you develop in house or outsource. Whether the device runs software or AI.
Out of that comes a map of every process, procedure, and work instruction your company needs in order to be compliant. It is built against your product and your markets. The map starts with what gets you to submission, design and development and risk, and works outward from there. You keep it whether or not you go any further.
Build it.
We pull the matching documents from our own body of IP, then tailor them. Terminology first: if your company calls it design rather than R&D, your procedures say design. Then structure, so the system matches how your team is organized instead of how a template assumed it would be.
Validate it.
The system deploys with its validation documentation. When an auditor asks how your eQMS was qualified, you have the record, and it was produced as part of the build rather than reconstructed afterwards. Your team is trained on the workflows they will own. Proxi monitors from day one.
Where the documents come from
Documents already through FDA and EU MDR audits
A template library is written to be generic, because it has to fit everyone who buys it. The documents we start from were written for real device companies and then tested by real inspections.
That is a different kind of starting point. The language, the structure, and the level of detail have already survived the only review that counts.
- Rev ETailored to your terminologyCurrent
- Rev DEU MDR auditSuperseded
- Rev CFDA inspectionSuperseded
What eight weeks looks like
eQMS implementation in about eight weeks
- To start
The mapping session
We map what your product and markets require, with you.
- Within 48 hours
Provisioning
The team takes the map to the provisioning system and selects the document suites and workflows that apply to your product. Your base procedures and a glossary of your applicable regulations land in your system.
- Weeks one to six
Six working sessions
About 90 minutes each, recorded and handed to you. Each one teaches why a regulation is there and how the workflow that satisfies it runs, and your documents and workflows get tailored to your company as you go.
- Six to seven days
Freeze and validation
Once your documents and workflows are yours, the system is frozen and validated for your company specifically. The validation documentation is released into your system, so when an auditor asks how the eQMS was qualified you have the evidence.
- The final days
Signing
Every document is routed through document control, everyone signs, and you are live.
Who does what
Who does the work, and when
| Task | With a template library | With us |
|---|---|---|
| Working out which procedures apply | You, or a consultant you hire | The mapping session |
| Writing the procedures | You | Pulled from audited IP and tailored |
| Matching terminology to your company | You | Included |
| Validating the system | You, or a separate vendor | Included, with the documentation |
| Training your team | Often a paid add-on | Included |
| Keeping it current | You | Proxi flags it, a person resolves it. Critical items cannot move forward until they are addressed |
Common questions
Common questions
What do you need from us to start?
Time in one working session, and honest answers about what you make and where you intend to sell it. You do not need existing documentation, a quality manager, or anything prepared in advance. If you do have documents already, bring them.
What if our product changes during the build?
Tell us. A change in product class, a new market, or software or AI appearing in the device changes which procedures apply. It is far cheaper to adjust during the build than to retrofit afterwards. This is one of the reasons the map exists before the build starts.
Do we need a quality manager to run it afterwards?
No, and that is largely a function of what is inside the system, and much less of the software. Because your procedures are written for your product and your team, a founder or a fractional consultant can operate it. An empty platform with a template library is what needs a specialist.
Who owns the documents?
You own your documents. The base procedures come from our IP, and what you receive is a lifetime license to the versions tailored to your company, in your terminology. They are yours and they leave with you if you ever go elsewhere. The workflows that run them inside the platform are IntelaSolve’s, which is what you are licensing when you license the platform.
What happens after go-live?
The system is yours and it is running. Proxi monitors it continuously, flagging what needs attention instead of waiting for a periodic review to catch it. The annual platform fee covers the system from that point.
See the plan before you commit
The mapping session comes before any of this. It produces the plan: what your system has to contain, and what building it involves for a company like yours.
You see that first. The map is yours to keep either way.