Lifen website screenshot

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 28 more developer resources.

🌐 Visit website 📡 Source on GitHub
59.5/100 strong ▬ flat Agent 48/100 agent ready Full breakdown ↓
scored 2026-08-17 · rubric v0.11.0
AccessSelf serve
7 APIs 1 MCP Servers
CompanyHealthcareFHIRInteroperabilityHealth DataElectronic Health RecordsMedical DocumentsSecure MessagingFranceHL7

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 59.5/100 · strong
Contract Quality 13.8 / 21
Developer Ergonomics 11.4 / 17
Commercial Clarity 7.2 / 17
Operational Transparency 8.4 / 11
Governance 2.1 / 10
Discoverability 7.9 / 9
Regulatory Posture 8.8 / 15
Agent readiness — 48/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
MCP Server 12 / 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
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/. 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. Want it done for you? Prioritized profiling — $2,500 →

APIs 7

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

Lifen CommunicationRequest API

The CommunicationRequest API from Lifen — 3 operation(s) for communicationrequest.

Lifen Coverage API

The Coverage API from Lifen — 1 operation(s) for coverage.

Lifen Encounter API

The Encounter API from Lifen — 2 operation(s) for encounter.

Lifen Organization API

The Organization API from Lifen — 1 operation(s) for organization.

Lifen Patient API

The Patient API from Lifen — 2 operation(s) for patient.

Lifen Practitioner API

The Practitioner API from Lifen — 1 operation(s) for practitioner.

Lifen Token API

The Token API from Lifen — 1 operation(s) for token.

Scroll for all 7

Postman Collections 7

Ready-to-run Postman collections for exercising this provider's APIs.

lifen-authentication-api CommunicationRequest API

POSTMAN

lifen-authentication-api CommunicationRequest Coverage API

POSTMAN

lifen-authentication-api CommunicationRequest Encounter API

POSTMAN

lifen-authentication-api CommunicationRequest Organization API

POSTMAN

lifen-authentication-api CommunicationRequest Patient API

POSTMAN

lifen-authentication-api CommunicationRequest Practitioner API

POSTMAN

lifen-authentication-api CommunicationRequest Token API

POSTMAN

Scroll for all 7

Open Collections 8

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

lifen-authentication-api CommunicationRequest API

OPEN COLLECTION

lifen-authentication-api CommunicationRequest Coverage API

OPEN COLLECTION

lifen-authentication-api CommunicationRequest Encounter API

OPEN COLLECTION

lifen-authentication-api CommunicationRequest Organization API

OPEN COLLECTION

lifen-authentication-api CommunicationRequest Patient API

OPEN COLLECTION

lifen-authentication-api CommunicationRequest Practitioner API

OPEN COLLECTION

lifen-authentication-api CommunicationRequest Token API

OPEN COLLECTION

Scroll for all 8

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

lifen-mcp.yml

MCP SERVER

Rate Limits 1

Documented rate limits and quota policies.

Lifen Rate Limits

6 limits

RATE LIMITS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Lifen Platform Webhooks

ASYNCAPI

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Lifen Authentication

oauth2/openIdConnect/apiKey · 3 schemes

SECURITY

Lifen Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

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
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
 MCPServer
MCPServer

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conventions
Conventions
 ErrorCatalog
ErrorCatalog
 Lifecycle
Lifecycle
 Conformance
Conformance
 Webhooks
Webhooks
 DataModel
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
DomainSecurity
 Compliance
Compliance
 Authentication
Authentication
 OAuthScopes
OAuthScopes

Operate 5

Status, limits, changes, and where to get help

Support
Support
 StatusPage
StatusPage
 ChangeLog
ChangeLog
 ChangeLog
ChangeLog
 RateLimits
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 1

Properties that don't map to a standard resource type

Overlay
Overlay

Source (apis.yml)

apis.yml Raw ↑ 
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
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.20'
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: 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: MCPServer
  url: mcp/lifen-mcp.yml
- 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