# Developer tools

**Portal version:** 0.1.0  
**Updated:** 2026-08-28  
**Source menu item:** Tools  
**Availability:** Documented and testable

> The source contract and local workflow exist. Access still depends on the target hospital deployment and its policy gates.

Use the scaffold, loopback bridge simulator, FHIR/Postman assets, schema validators, sample app, and readiness probes.

## What you can use now

- The lab-result-viewer example is synthetic and TEST-only.
- Marketplace verification distinguishes source readiness from anonymous public availability.

## Current limits

- No tool output is runtime authority.

## Next step

Start with the [medOS Developer overview](/developers/platform/overview) and confirm the target hospital’s enabled contracts before production work.

## Canonical references

- [FHIR R4 integration](/integrations/fhir)
- [Public API](/backend/public-api)
- [Security and compliance](/architecture/security-and-compliance)
- [Developer portal status and coverage](/developers/platform/changelog)