# MedVertical

> MedVertical builds Records for FHIR conformance and dataset quality: agreed checks, concrete findings, comparable runs, and reviewable results for releases and data handovers.

MedVertical is based in Cologne, Germany and was founded by André Sheydin. Records supports release, handover, integration, research, and agent-driven FHIR workflows. It emits PASS, WARN, and FAIL signals; people and governed workflows remain responsible for clinical, compliance, certification, acceptance, and release decisions.

Current public versions: Records 0.13.0, `@records-fhir/validator` 0.7.0, `@records-fhir/cli` 0.1.1, and Records Agent Tools 0.8.4. Detailed compatibility and dated evidence remain authoritative over summaries.

Automated validation is read-only by default. Selected FHIR resources are processed transiently, while derived findings, run context, evidence records, and integrity metadata can persist according to the deployment policy. MedVertical currently claims no ISO 27001, SOC 2, or HIPAA certification.

## Product

- [Try Records](https://medvertical.com/records/demo): Overview of public-server browsing, validation context, and the synthetic-resource sandbox.
- [Open public demo](https://records.medvertical.com/demo): Browse public FHIR test resources without an account.
- [Sandbox walkthrough](https://medvertical.com/records/demo#sandbox): Check one synthetic resource and try a correction without saving workspace evidence.
- [Plan an evaluation](https://medvertical.com/hosted-access): Evaluate one permitted dataset with agreed checks and a correction cycle. Workspace access is staged; scope, timing, and terms are confirmed before starting.
- [Records](https://medvertical.com/records): Product overview, release-quality loop, operating boundary, and current Records version.
- [Use cases](https://medvertical.com/use-cases): Release, drift, comparison, evidence, research, reporting, CI/CD, and agentic FHIR decisions.
- [Deployment](https://medvertical.com/deployment): Public, hosted, and customer-managed operating models.
- [Enterprise](https://medvertical.com/enterprise): Data, identity, evidence, procurement, and qualification boundaries.
- [Trust and security](https://medvertical.com/trust): What Records reads, stores, and can change.
- [Compatibility](https://medvertical.com/compatibility): FHIR-release, package, server, and validation-lane support.

Records DQM adds versioned indicators for completeness, uniqueness, and reference integrity within a selected dataset. Results carry scope, policy, evaluated population, and not-evaluable cases. The MII-oriented indicators are independently defined operational checks, not normative MII requirements or certification. Repeating a run requires the corresponding data and dependencies as well as the recorded evaluation context.

## Developer interfaces

- [Developer hub](https://medvertical.com/developers): Choose the validator, CLI, Records Agent Tools, or MCP integration surface.
- [TypeScript validator](https://medvertical.com/developers/validator): Apache-2.0 in-process FHIR validation.
- [Records CLI](https://medvertical.com/developers/cli): Local and CI validation with machine-readable output.
- [Records Agent Tools](https://medvertical.com/developers/claude-code): Local FHIR validation and project diagnostics for Claude Code and Codex.
- [Records MCP server](https://medvertical.com/developers/mcp): Tenant-scoped validation and run context for compatible agents.
- [Validator evidence](https://medvertical.com/validator): Current package version and dated Java-parity evidence.

## Market and implementation context

- [Germany](https://medvertical.com/germany): Version-specific ISiK, MII, KBV, and HL7 DE context.
- [CMS readiness](https://medvertical.com/cms-readiness): Independent validation evidence around CMS FHIR API implementation work.
- [HL7 Europe Base/Core 2.0](https://medvertical.com/resources/hl7-europe-base-core-2-0): Concrete validation evidence example.
- [EHDS readiness lab](https://medvertical.com/resources/ehds-implementation-readiness-lab): Reproducible implementation exercise with clean and broken fixtures.
- [FHIR validation blog](https://medvertical.com/blog): Long-form technical analysis with authorship, dates, and source references.
- [FAQ](https://medvertical.com/faq): Product, deployment, assurance, compatibility, and data-boundary answers.

## Machine-readable context

- [Full product context](https://medvertical.com/llms-full.txt): Expanded product, developer, compatibility, deployment, and decision-boundary context.
- [Site index in Markdown](https://medvertical.com/index.md): Concise orientation and canonical route map.
- [Records in Markdown](https://medvertical.com/records.md): Product definition, release-quality loop, and usage paths.
- [Product primitives in JSON](https://medvertical.com/primitives.json): Stable machine-readable positioning, invariants, versions, and data-handling fields.
- [Approach in Markdown](https://medvertical.com/approach.md): Evidence-not-authority and boundary-discipline principles.

## Company

- [About MedVertical](https://medvertical.com/about): Company history, founder, and operating principles.
- [Contact](https://medvertical.com/contact): Product, technical, research, and partnership contact.
- [GitHub organization](https://github.com/medvertical): Public source repositories and releases.