Aidbox
Search…
Aidbox documentation
Overview
Licensing and Support
Features
Aidbox user portal
Aidbox UI
Versioning
Release Notes
FAQ
Getting Started
Run Aidbox locally with Docker
Run Multibox locally with Docker
Run Aidbox in Aidbox Sandbox
Run Aidbox with non-privileged postgresql role
Run Aidbox as a SaaS
Run Aidbox in Kubernetes
Aidbox configuration
Configure Aidbox and Multibox
Aidbox project
API constructor (beta)
Setup SMTP provider
Zen Configuration
API
FHIR API
REST API
Bulk API
Batch Upsert
Batch/Transaction
Cache
ETAG support
Reactive API
Sequence API
Encryption API
Compartments API
GraphQL API
RPC API
Profiling and validation
Profiling and validation overview
Profiling with zen-lang
Asynchronous resource validation
Profiling with AidboxProfile
Terminology
Aidbox terminology module overview
Create a ValueSet
Import external terminologies
Concept
CodeSystem
ValueSet
Handling hierarchies using ancestors
$translate on ConceptMap
Terminology Tutorials
FHIR Implementation Guides
🎓
HL7 FHIR Da Vinci PDex Plan Net IG
§170.315(g)(10) Standardized API for patient and population services
Tutorials
App development guides
Testing with Stresty
Working with Aidbox from .NET
Administration
Receive logs from your app
$matcho
$to-format
Storage
AidboxDB
Database schema
Archiving
AWS S3
GCP Cloud Storage
Azure Blob Storage
Oracle Cloud Storage
Security & Access Control
Overview
Authentication Flows
Access Control
Multitenancy
Core Modules
Entities & Attributes
$json-schema
Monitoring
Logging & Audit
Modules
HL7 v2 Integration
CCDA
FHIR Resources
Custom Resources
Aidbox Search
First-Class Extensions
Aidbox Forms
SMARTbox
Multibox
Multibox box manager API
Multibox monitoring
Plan API
Plan API Overview
Patient Access API
Integrations
Analytics
Audit
Authentication
Email providers
Tools
Mappings
Aidbox SDK
Contact us
Reference
Configuration
Aidbox Forms reference
Powered By
GitBook
$to-format
Debug conversion between Aidbox and FHIR formats
Aidbox converts
FHIR and AIdbox formats
on the fly. To debug this transformation, you can use
POST /$to-format/fhir
and
POST /$to-format/aidbox
endpoints, which can show you the result of your transformation with some additional info:
POST /$to
-
format/aidbox
resourceType
:
Observation
valueString
:
test
# 200
# result of transformation
resource
:
resourceType
:
Observation
value
:
{
string
:
test
}
# dsl which is used for transformation
transform
:
hasMember
:
{
tr/reference
:
true
,
tr/ref
:
Reference
,
tr/isCollection
:
true
}
derivedFrom
:
{
tr/reference
:
true
,
tr/ref
:
Reference
,
tr/isCollection
:
true
}
...
And back:
POST /$to
-
format/fhir
resourceType
:
Observation
value
:
string
:
test
# 200
resource
:
resourceType
:
Observation
valueString
:
test
transform
:
hasMember
:
{
tr/reference
:
true
,
tr/ref
:
Reference
,
tr/isCollection
:
true
}
derivedFrom
:
{
tr/reference
:
true
,
tr/ref
:
Reference
,
tr/isCollection
:
true
}
encounter
:
{
tr/reference
:
true
,
tr/ref
:
Reference
}
Notes:
How to read transform DSL
tr/reference
- instruction to transform references
tr/ref
- recursively go to type definition or follow content-ref
tr/union
- translate union / choice types
tr/ext
- translate known extensions
App development guides - Previous
$matcho
Next - Storage
AidboxDB
Last modified
1yr ago
Copy link
Edit on GitHub