Skip to main content


A workspace is an isolated, billable unit of infrastructure that functions as a fully-loaded FHIR server with additional capabilities. As a developer of applications, you can provision a workspace for the following use cases:

  • Dedicated FHIR API for CRUDS operations.
  • Extending other FHIR APIs functionality, such as enabling the creation of new resources even if it's forbidden by default.
  • Persist FHIR, blob or structured data in a data vault.
  • Make C-CDA documents available as FHIR via an API.

The MeldRx workspace is a platform that redefines the development experience by seamlessly integrating a data vault, our identity management system, a complete FHIR API and so much more, within a singular environment. MeldRx offers three types of workspaces: standalone, linked, and anonymous.

Standalone workspace

Standalone workspaces are FHIR servers ready for independent use, capable of handling FHIR resources, managing patient data, and supporting healthcare applications without needing integration with an existing EHR. Standalone workspaces may be a good fit if you're looking for:

  • EHR-connected solutions (e.g. sidecar applications)
  • Consumer Mediated Exchange (You can learn more on our blog)
  • FHIR-first solutions (e.g. headless EHRs or registries)

Linked workspace

Linked workspaces grant developers the freedom to connect their workspaces to any EHR or FHIR server, facilitating data exchange and functionality integration in ways previously unattainable. They also enhance the EHR integration experience by providing app developers with the tools needed to fill in gaps and deficiencies in the EHR. For example, if an EHR does not allow writing data back, your apps can write data directly to the workspace. Linked workspaces may be a good choice if you're looking for:

  • Getting real-time data from EHRs.
  • Writing data directly to EHRs (where supported).
  • Use cases involving reading or writing clinical, billing, or device data such as CGM to/from EHRs.

Anonymous workspace

An anonymous workspace implements all the standard capabilities of a FHIR server without requiring the users to authenticate, making it easier for broad public use. This limits the FHIR server to only provide access to non-sensitive, de-identified, or aggregated healthcare data to ensure privacy and regulatory compliance.

Why would I want an anonymous workspace?

  • Sharing aggregated health statistics and trends for public awareness and research.
  • Providing de-identified datasets for training and educational purposes in medical or research institutions.
  • Offering access to clinical best practices and standardized terminologies.
  • Allowing developers to test applications against FHIR APIs without needing credentials.

Interested in an anonymous workspace? Contact us.