Collaborative specification processes in the enterprise
summary
Philips builds an internal ILS that profiles FHIR, IHE and DICOM into reusable interaction patterns and publishes them from GitHub as versioned npm packages. Specs live as OpenAPI/Swagger YAML, include OAuth scopes, PlantUML diagrams, and CI pipelines that auto-publish to an API management registry; tests are moving from manual to automated based on OpenAPI. The process uses GitHub pull requests for discussion and OpenAPI/Swagger driven code/test generation; outcome: fewer duplicate point-to-point integrations and faster product composition.
AI-written summary · about
chapters (13)
- 0:00Cross-Philips Architecture Alignment
- 4:04To: Standardized Integrations
- 6:16Interoperability: Foundational
- 7:30Interoperability: Structural
- 8:04Interoperability: Semantic
- 9:01Interoperability: Organizational
- 10:01Philips Interoperability Language System (ILS)
- 11:06Healthsuite API view on solutions
- 16:24Interaction Pattern Ingredients
- 18:15Patient Data Exchange Pattern
- 21:53Interaction Pattern Specification Content (inspired by IHE ITI patterns)
- 26:08Interaction Pattern Structure
- 27:46Example API definition based on FHIR Rest API
related talks
36mPlan, Specify, and Implement
26mBuilding APIs for Developers & Machines
29mTooling
37mSpec Driven Development: AI Assisted Coding With Doc at the Core
23mStop Making LLMs Deterministic: A Spec-Driven Software Factory
32mProject API Forge: Streamlining Dev-First API Lifecycle Management.
24mBuilding an Accessible API Spec with Traditional Engineering Teams
21mLet there be docs!