Register Organization¶

Each customer organization in your system needs to be registered in Unomed before you can send patient data. This is a one-time setup per organization.

See the API Documentation for full endpoint details.

As a primary software integrator, you will have multiple customer organizations. Create each organization in Unomed when they first use the integration.

immer den gleichen benutzen für den gleichen identifier "system": "https://your-system.ch/",

Create Organization¶

curl -X POST https://api.dev.unomed.ch/fhir/r4/Organization \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -H "Content-Type: application/fhir+json" \
  -d '{
    "resourceType": "Organization",
    "identifier": [{
      "system": "https://your-system.ch/",
      "value": "customer-org-123"
    }],
    "name": "Customer Organization Name",
    "active": true
  }'

Required Fields¶

Field	Description
`name`	Organization display name

Recommended Fields¶

Field	Description
`identifier.system`	A URI identifying your primary system (e.g., `https://your-system.ch/`)
`identifier.value`	The customer organization's ID in your system (e.g., `customer-org-123`)

Using identifiers helps you look up organizations later without storing Unomed UUIDs.

Response¶

{
  "resourceType": "Organization",
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "identifier": [...],
  "name": "Customer Organization Name",
  "active": true
}

Save the id - you need it when creating patients and launching the PopApp.

Check if Organization Exists¶

Query by identifier value (not system|value):

curl "https://api.dev.unomed.ch/fhir/r4/Organization?identifier=customer-org-123" \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN"

This returns organizations matching the identifier value.