Aidbox
Aidbox.Dev
Aidbox.Cloud
Aidbox.One
Fhirbase
Search…
Getting started
Getting Started
Installation & Configuration
Features
Licensing and Support
Versioning & Release Notes
FAQ
Aidbox configuration
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
Aidbox UI
Profiling and validation
Profiling and validation overview
Profiling with zen-lang
Asynchronous resource validation
Profiling with AidboxProfile
Terminology
Aidbox terminology module overview
Import external (not-present) terminologies
Concept
CodeSystem
ValueSet
$translate on ConceptMap
Terminology Tutorials
FHIR Implementation Guides
🎓
HL7 FHIR Da Vinci PDex Plan Net IG
App development guides
Tutorials
Administration
Receive logs from your app
$matcho
$to-format
Security & Access Control
Overview
Authentication Flows
Access Control
Multitenancy
Storage
Archiving
Database
AWS S3
GCP Cloud Storage
Azure Blob Storage
Core Modules
Entities & Attributes
$json-schema
Monitoring
Logging & Audit
Modules
HL7 v2 Integration
FHIR Resources
Custom Resources
Aidbox Search
First-Class Extensions
Multibox
Multibox box manager API
Plan API
Plan API Overview
Patient Access API
Integrations
Analytics
Audit
Authentication
Tools
Mappings
Aidbox SDK
Contact us
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:
1
POST /$to
-
format/aidbox
2
​
3
resourceType
:
Observation
4
valueString
:
test
5
​
6
# 200
7
​
8
# result of transformation
9
resource
:
10
resourceType
:
Observation
11
value
:
{
string
:
test
}
12
# dsl which is used for transformation
13
transform
:
14
hasMember
:
{
tr/reference
:
true
,
tr/ref
:
Reference
,
tr/isCollection
:
true
}
15
derivedFrom
:
{
tr/reference
:
true
,
tr/ref
:
Reference
,
tr/isCollection
:
true
}
16
...
Copied!
And back:
1
POST /$to
-
format/fhir
2
​
3
resourceType
:
Observation
4
value
:
5
string
:
test
6
​
7
# 200
8
resource
:
9
resourceType
:
Observation
10
valueString
:
test
11
transform
:
12
hasMember
:
{
tr/reference
:
true
,
tr/ref
:
Reference
,
tr/isCollection
:
true
}
13
derivedFrom
:
{
tr/reference
:
true
,
tr/ref
:
Reference
,
tr/isCollection
:
true
}
14
encounter
:
{
tr/reference
:
true
,
tr/ref
:
Reference
}
Copied!
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 - Security & Access Control
Overview
Last modified
1yr ago
Copy link
Contents