Building on FHIR requires a FHIR-first menatlity. That means if you can build something in FHIR you will build it in FHIR. This approach enables the interoperability created by the community of EHRs, governments, applications, and researchers contributing to the spec.
Our entire Built on FHIR stack is deployed using serverless architecture benefiting from the horizontally scaleable technology of the cloud. Ultimately this leads to faster response time, linear scaleability, and better security with nearly zero downtime.
Whatever data we get we convert into FHIR. This means HL7v2/3, CCDA, documents, FHIR-ish, and other API data are all converted to the canonical FHIR Specification.
When any data lands in 1up, we store it in a FHIR native format (JSON) at the resource level in a document datastore. This way there are no requirements for SQL joins or need to compose a resource. You get it immediately. Data is sharded at the user level to improve performance. Each 1up customer's data is logically seperated by their app's client and consumer ids. There is never any overlap or sharing of data among our customers.
Each FHIR Resource is replicated into multiple data stores to support various data access patterns. Technically, different stores are optimized for specific use cases. Some are better for search operations, others for analytics, and others for read / write consistency. API queries to 1up's FHIR APIs are routed to the appropriate data store automatically to offer the highest possible performance.
Read and write functionality is provided to client applications using the full bredth of FHIR standard APIs. In fact, our team is helping set these standards with the support of HL7 and the ONC of the US government. In addition to standard FHIR APIs, we offer ANSI SQL support.
Whatever your application, interface, or organization builds on the 1up FHIR platform you can be sure it's buit with a FHIR-first mentality. You can take advantage of this entire stack in literally minutes assured that improvements are always coming.