Academy
⌘K
Getting Started
  • Platform Overview
  • AWS Marketplace Setup
  • Quickstart Guide
Connections
  • Overview
Workflow Builder
  • Overview
  • Nodes Catalog
Helix AI Assistant
  • Overview
Mapping Engine
  • Overview
Workflow Library
  • Overview
  • HL7
  • FHIR
  • Insurance
  • Agentic
  • Mapping
Security & Infrastructure
  • Architecture
  • HIPAA Compliance
  • Performance & Scalability
← Back to ConnectHealth
Get Started
Back to Nodes
FHIR1 input → 1 output

FHIR Create

payload.access… (string)payload.resource (object)payload.resour… (string)FHIRFHIR Createpayload (object)fhir.resourceT… (string)fhir.resourceId (string)Data flowProperty

Creates a new FHIR resource on the server.

Inputs

payload.access_token string
Access token for FHIR server authentication (required)
payload.resource object
FHIR resource object to create. Must include resourceType. Overrides node configuration
payload.resourceType string
FHIR resource type to override the one in the resource object

Outputs

payload object
The created FHIR resource with server-assigned ID
fhir object
Metadata about the FHIR operation:
  • resourceType - Type of resource created
  • resourceId - Server-assigned ID of created resource
  • url - Full FHIR URL of created resource
  • integrationId - Integration used
  • operation - Always "create"

Details

This node performs a FHIR create operation to add a new resource to the server.

The node requires an access token to be provided in msg.payload.access_token. This token should have appropriate permissions to create the requested resource type.

The FHIR resource can be provided in the node configuration or via msg.payload.resource. Message values take precedence over node configuration.

The resource must be a valid FHIR resource object with at minimum a resourceType field. The server will validate the complete resource structure.

The created resource with its server-assigned ID will be returned in the payload.

Scope Validation

The node checks if the selected resource type is included in the integration's scopes. Create operations require write or create permissions.

Scopes follow the format: [user|patient|system]/[ResourceType|*].[permissions]

For create operations, valid permissions include:

  • c - Create permission
  • w or write - Write permission (includes create)
  • * - All permissions
  • Combined permissions like crud, cw, etc.

Examples:

  • patient/*.c - Can create all resource types in patient context
  • user/Patient.write - Can write/create Patient resources in user context
  • system/Observation.* - Can perform all operations on Observations

Best Practices

  • Validate resource structure before submitting to server
  • Always include required FHIR fields (resourceType)
  • Use server-assigned IDs rather than client-assigned when possible
  • Handle duplicate creation errors gracefully
  • Store returned resource ID for future reference operations
  • Validate against FHIR profiles when required by integration