# Get started

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

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

Create a project, run doctor and tests, then preview a synthetic bridge exchange on loopback.

## What you can use now

- Use the template CLI and `.env.example`; never copy a real `.env` into the project or release.
- Package the kit only after the full test suite passes.

## Quick example

```bash
node bin/medos-app.mjs create ../my-app --app-id my-app --publisher-id my-team
cd ../my-app
npm test
npm run doctor
```

## Current limits

- The quickstart creates authoring material only.

## 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)