Skip to content

Latest commit

 

History

History
48 lines (28 loc) · 2.94 KB

File metadata and controls

48 lines (28 loc) · 2.94 KB

How We Work

Building in Public

This isn't a product announcement. We don't have a polished landing page or a sales deck. What we have is a clear vision, working code, and the conviction that pharma needs this — now.

We're building Mediforce in the open because we believe the best way to create a standard is to create it together. We want input from people who work in clinical operations, from developers who build for regulated industries, from compliance experts who know what "GxP-ready" actually requires.

Our Approach

Bottom-Up, Not Top-Down

We don't start with a grand abstraction and hope it fits reality. We start with real processes, build working applications, and extract the platform patterns as they emerge. Every abstraction in Mediforce earns its place by being needed in more than one concrete use case.

Code-First

Mediforce is a developer platform, not a drag-and-drop builder. We believe that code is the most precise, version-controllable, and AI-friendly way to define processes. Good APIs, clear documentation, and TypeScript throughout.

That said, AI coding assistants make code-first accessible to people who think in processes, not in syntax.

Real Processes, Real Complexity

Every feature we build is validated against real pharma processes — parallel steps, review loops, multiple agents with different autonomy levels, compliance gates, and complex data models. If the platform handles that, simpler processes are easy.

The Team

Mediforce is built by Appsilon — a company that has been building data solutions for life sciences since 2013. We've worked with some of the largest pharma companies in the world, building production software for clinical operations, biostatistics, and data science teams.

We started building an application for a pharma process and realized: every pharma company will need this infrastructure. It shouldn't be reinvented for every project. It should be a standard.

Contributing

We're in early stages and actively looking for:

  • Domain experts — people who work in clinical operations, pharmacovigilance, regulatory, supply chain. Your knowledge of real processes is what makes Mediforce useful.
  • Developers — interested in building for regulated industries, workflow systems, or human-AI collaboration.
  • Compliance professionals — who can help us get GxP-readiness right from the start.

The best way to contribute right now:

  1. Join our Discord and share your perspective
  2. Open an issue describing a process you'd want to see on the platform
  3. Come to a Friday working session (3:00 PM CEST, weekly) — ask questions, give feedback, see what we're working on

Staying Updated

  • Discord — real-time conversations and progress updates
  • GitHub — star the repo, watch for updates
  • Blog — longer-form posts on appsilon.com/blog