Lifen

Lifen (Honestica SAS, Paris) is a French digital-health company whose Lifen Platform exposes FHIR R4 APIs that let e-health applications exchange health data with French hospital information systems and with healthcare professionals over the national MSSanté secure-messaging network. The platform is organised as API Services: Hospital API Services (an Identity & Encounter service giving secure access to patient administrative, coverage, encounter and appointment data inside a given hospital, and a Send-documents-to-EHR service that pushes medical documents into hospital Electronic Health Records), and National API Services (the MSS service for sending medical documents to healthcare professionals via MSSanté). Access is machine-to-machine over OAuth 2.0 client credentials, scoped by functional scopes and bound to a healthcare organisation through a database_reference. Lifen also ships an SSO/OIDC API and a signed webhook surface for patient and encounter events. The company is ISO 27001 certified and an HDS (Hebergeur de Donnees de Sante) certified health-data host.

Lifen publishes 7 APIs on the APIs.io network, including CommunicationRequest API, Coverage API, Encounter API, and 4 more. Tagged areas include Company, Healthcare, FHIR, Interoperability, and Health Data.

The Lifen catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Lifen’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, signup flow, changelog, and 29 more developer resources.

🌐 Visit website 📡 Source on GitHub

57.1/100 strong ▬ flat Agent 39/100 agent ready saas Full breakdown ↓
scored 2026-09-06 · rubric v0.19.0

AccessSelf serve

2 APIs

Company Healthcare FHIR Interoperability Health Data Electronic Health RecordsMedical DocumentsSecure Messaging France HL7

Kin Score

Kin Score How this is scored →
scored 2026-09-06 · rubric v0.19.0

Composite quality — 57.1/100 · strong

Contract Quality 12.4 / 21

Developer Ergonomics 8.4 / 17

Access Clarity 7.2 / 17

Operational Transparency 6.4 / 11

Contract Governance 1.9 / 10

Discoverability 6.5 / 9

Regulatory Posture 9.8 / 15

Agent readiness — 39/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/lifen: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 7

Individual APIs this provider publishes, each with its own machine-readable definition.

Rate Limits 1

Documented rate limits and quota policies.

Scopes 1

OAuth scopes governing access to this provider's APIs.

Lifen Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Get Started 5

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Login

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

WellKnown

WellKnown

AgentSkill

AgentSkill

X-MCPServerCandidate

X-MCPServerCandidate

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

Webhooks

DataModel

Build 3

SDKs, sample code, and the tooling you integrate with

PostmanWorkspace

PostmanWorkspace

GitHubOrganization

GitHubOrganization

Postman

Postman

Access & Security 4

Authentication, authorization, and security posture

DomainSecurity

Compliance

Authentication

OAuthScopes

Operate 5

Status, limits, changes, and where to get help

Support

StatusPage

ChangeLog

ChangeLog

RateLimits

Commercial 3

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

LegalNotice

LegalNotice

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: lifen
name: Lifen
description: 'Lifen (Honestica SAS, Paris) is a French digital-health company whose Lifen Platform exposes FHIR R4 APIs that
  let e-health applications exchange health data with French hospital information systems and with healthcare professionals
  over the national MSSanté secure-messaging network. The platform is organised as API Services: Hospital API Services (an
  Identity & Encounter service giving secure access to patient administrative, coverage, encounter and appointment data inside
  a given hospital, and a Send-documents-to-EHR service that pushes medical documents into hospital Electronic Health Records),
  and National API Services (the MSS service for sending medical documents to healthcare professionals via MSSanté). Access
  is machine-to-machine over OAuth 2.0 client credentials, scoped by functional scopes and bound to a healthcare organisation
  through a database_reference. Lifen also ships an SSO/OIDC API and a signed webhook surface for patient and encounter events.
  The company is ISO 27001 certified and an HDS (Hebergeur de Donnees de Sante) certified health-data host.'
url: https://raw.githubusercontent.com/api-evangelist/lifen/refs/heads/main/apis.yml
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://files.readme.io/ea56e58-small-Logo_couleur.png
x-type: company
x-source: vc-portfolio
x-backed-by:
- partech
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- Healthcare
- FHIR
- Interoperability
- Health Data
- Electronic Health Records
- Medical Documents
- Secure Messaging
- France
- HL7
apis:
- aid: lifen:lifen-communicationrequest-api
  name: Lifen CommunicationRequest API
  description: The CommunicationRequest API from Lifen — 3 operation(s) for communicationrequest.
  humanURL: https://developer.lifen.fr/reference/patient
  baseURL: https://api.lifen.fr/fhir/v3
  tags:
  - CommunicationRequest
  properties:
  - type: OpenAPI
    url: openapi/lifen-communicationrequest-api-openapi.yml
  - type: Documentation
    url: https://developer.lifen.fr/docs/platform-services-documentation
  - type: APIReference
    url: https://developer.lifen.fr/reference/patient
  - type: Documentation
    url: https://developer.lifen.fr/docs/machine-to-machine-communications
- aid: lifen:lifen-coverage-api
  name: Lifen Coverage API
  description: The Coverage API from Lifen — 1 operation(s) for coverage.
  humanURL: https://developer.lifen.fr/reference/patient
  baseURL: https://api.lifen.fr/fhir/v3
  tags:
  - Coverage
  properties:
  - type: OpenAPI
    url: openapi/lifen-coverage-api-openapi.yml
  - type: Documentation
    url: https://developer.lifen.fr/docs/platform-services-documentation
  - type: APIReference
    url: https://developer.lifen.fr/reference/patient
  - type: Documentation
    url: https://developer.lifen.fr/docs/machine-to-machine-communications
- aid: lifen:lifen-encounter-api
  name: Lifen Encounter API
  description: The Encounter API from Lifen — 2 operation(s) for encounter.
  humanURL: https://developer.lifen.fr/reference/patient
  baseURL: https://api.lifen.fr/fhir/v3
  tags:
  - Encounter
  properties:
  - type: OpenAPI
    url: openapi/lifen-encounter-api-openapi.yml
  - type: Documentation
    url: https://developer.lifen.fr/docs/platform-services-documentation
  - type: APIReference
    url: https://developer.lifen.fr/reference/patient
  - type: Documentation
    url: https://developer.lifen.fr/docs/machine-to-machine-communications
- aid: lifen:lifen-organization-api
  name: Lifen Organization API
  description: The Organization API from Lifen — 1 operation(s) for organization.
  humanURL: https://developer.lifen.fr/reference/patient
  baseURL: https://api.lifen.fr/fhir/v3
  tags:
  - Organization
  properties:
  - type: OpenAPI
    url: openapi/lifen-organization-api-openapi.yml
  - type: Documentation
    url: https://developer.lifen.fr/docs/platform-services-documentation
  - type: APIReference
    url: https://developer.lifen.fr/reference/patient
  - type: Documentation
    url: https://developer.lifen.fr/docs/machine-to-machine-communications
- aid: lifen:lifen-patient-api
  name: Lifen Patient API
  description: The Patient API from Lifen — 2 operation(s) for patient.
  humanURL: https://developer.lifen.fr/reference/patient
  baseURL: https://api.lifen.fr/fhir/v3
  tags:
  - Patient
  properties:
  - type: OpenAPI
    url: openapi/lifen-patient-api-openapi.yml
  - type: Documentation
    url: https://developer.lifen.fr/docs/platform-services-documentation
  - type: APIReference
    url: https://developer.lifen.fr/reference/patient
  - type: Documentation
    url: https://developer.lifen.fr/docs/machine-to-machine-communications
- aid: lifen:lifen-practitioner-api
  name: Lifen Practitioner API
  description: The Practitioner API from Lifen — 1 operation(s) for practitioner.
  humanURL: https://developer.lifen.fr/reference/patient
  baseURL: https://api.lifen.fr/fhir/v3
  tags:
  - Practitioner
  properties:
  - type: OpenAPI
    url: openapi/lifen-practitioner-api-openapi.yml
  - type: Documentation
    url: https://developer.lifen.fr/docs/platform-services-documentation
  - type: APIReference
    url: https://developer.lifen.fr/reference/patient
  - type: Documentation
    url: https://developer.lifen.fr/docs/machine-to-machine-communications
- aid: lifen:lifen-token-api
  name: Lifen Token API
  description: The Token API from Lifen — 1 operation(s) for token.
  humanURL: https://developer.lifen.fr/reference/patient
  baseURL: https://api.lifen.fr/fhir/v3
  tags:
  - Token
  properties:
  - type: OpenAPI
    url: openapi/lifen-token-api-openapi.yml
  - type: Documentation
    url: https://developer.lifen.fr/docs/platform-services-documentation
  - type: APIReference
    url: https://developer.lifen.fr/reference/patient
  - type: Documentation
    url: https://developer.lifen.fr/docs/machine-to-machine-communications
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: CapabilityMap
  url: capabilities/lifen-capability-edges.yml
  name: Lifen Business Capability Map
- type: PostmanWorkspace
  url: https://www.postman.com/kinlaneapi/lifen/overview
- type: DomainSecurity
  url: security/lifen-domain-security.yml
- type: Website
  url: https://www.lifen.fr/
- type: DeveloperPortal
  url: https://developer.lifen.fr/
- type: Documentation
  url: https://developer.lifen.fr/docs/platform-services-documentation
- type: APIReference
  url: https://developer.lifen.fr/reference/patient
- type: GettingStarted
  url: https://developer.lifen.fr/docs/quickstart
- type: Support
  url: https://www.lifen.fr/contact
- type: Blog
  url: https://www.lifen.fr/ressources/blog
- type: GitHubOrganization
  url: https://github.com/honestica
- type: SignUp
  url: https://www.lifen.fr/sign-up
- type: Login
  url: https://www.lifen.fr/log-in
- type: TermsOfService
  url: https://www.lifen.fr/cgu
- type: PrivacyPolicy
  url: https://www.lifen.fr/donnees-personnelles
- type: LegalNotice
  url: https://www.lifen.fr/mentions-legales
- type: Postman
  url: https://developer.lifen.fr/docs/quickstart
- type: StatusPage
  url: https://status.lifen.fr/793930656
- type: ChangeLog
  url: https://developer.lifen.fr/changelog
- type: Compliance
  url: https://www.lifen.fr/nos-expertises/securite-des-donnees-de-sante
- type: LLMsTxt
  url: llms/lifen-llms.txt
- type: WellKnown
  url: well-known/lifen-well-known.yml
- type: Authentication
  url: authentication/lifen-authentication.yml
- type: OAuthScopes
  url: scopes/lifen-scopes.yml
- type: Conventions
  url: conventions/lifen-conventions.yml
- type: ErrorCatalog
  url: errors/lifen-problem-types.yml
- type: Lifecycle
  url: lifecycle/lifen-lifecycle.yml
- type: ChangeLog
  url: changelog/lifen-changelog.yml
- type: Conformance
  url: conformance/lifen-conformance.yml
- type: Webhooks
  url: asyncapi/lifen-platform-webhooks.yml
- type: AgentSkill
  url: skills/_index.yml
- type: X-MCPServerCandidate
  url: mcp/lifen-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: Overlay
  url: overlays/lifen-fhir-api-overlay.yaml
- type: Sandbox
  url: sandbox/lifen-sandbox.yml
- type: DataModel
  url: data-model/lifen-data-model.yml
- type: RateLimits
  url: rate-limits/lifen-rate-limits.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/lifen"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/lifen/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/lifen/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.