Azure API for FHIR

The Azure API for FHIR® is a managed, standards-based, and compliant healthcare data platform. It enables organizations to bring their clinical health data into the cloud based on the interoperable data standard FHIR®.

FHIR helps unlock the value of data and respond to changing business dynamics more easily.

Organizations are able to bring together clinical data from multiple systems of records, normalize the data using common models and specifications, and use that data in AI workloads to derive insight and power new systems of engagement, including clinician and patient dashboards, diagnostic assistants, population health insights, and connected healthcare scenarios, such as Remote Patient Monitoring.

The Azure API for FHIR is capable of powering Internet of Medical Things (IoMT) scenarios, population health research projects, AI-powered diagnostic solutions and much more.

The Azure API for FHIR meets all regulatory compliance for healthcare data.

Security and privacy are embedded into the service, which conforms to global health privacy and security standards. Customers own and control patient data, knowing how it is stored and accessed.

The services have been designed to handle live patient data (Protected Health Information, PHI)
  1. Operation $document on Composition

    Is support to generate a fully bundled document from a composition resource in the roadmap?

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  FHIR Standard Implementation  ·  Flag idea as inappropriate…  ·  Admin →
  2. Custom domain name

    It would really help if we were able to specify a custom domain name for an instance of Azure API for FHIR.

    Specifically when integrating with closed networks like the NHS network in the UK a DNS entry of xyz.nhs.uk is required and while this can be passed through to the FHIR server using the likes of Application gateway or API Management any resource URLS for retrieved data will have the wrong address making further lookups more difficult.

    being able to register the nhs.uk domain against the server would resolve this issue and allow for correct operation for any FHIR…

    2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  3. Does Azure API for FHIR support adding new resource types?

    My company is exploring whether Azure FHIR can be extended to store additional resource types. E.g. We want to store heart beat and running/walking data from a wearable device like FitBit/Garmin. Does Azure FHIR support such a scenario?

    2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. support for operation /Patient/<id>/$everything

    when will operation $everything from the fhir standard be supported.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  FHIR Standard Implementation  ·  Flag idea as inappropriate…  ·  Admin →
  5. Access to underlying cosmosdb

    When working with the FHIR standard we sometimes hit roadblocks where something doesnt work and we dont know if its our data or our searches etc

    It would really help in being able to investigate issues if a read only view into the underlying cosmos db instance was available, this could be just through the azure management portal but would allow us to interrogate and explore the underlying data store as we would if we were running our own instance of the FHIR server instead of using Azure API for FHIR.

    At the moment it seems too hard line of…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  6. Must support subscriptions from senders

    Many resources are Request Response. Normally the response is a 201. For the sender to receive a response, they need to subscribe to it.
    One example is the CoverageEligibityRequest. A 201 is returned to the sender. The CoverageEligibiltyResponse is not an automated response because the sender has already received the 201. In order for the sender to receive the response, they need to subscribe to it,

    This is not an idea it is a requirement

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Automation  ·  Flag idea as inappropriate…  ·  Admin →
  7. Azure API for FHIR

    A common task for developers is to investigate how to create a API FHIR server ... tools such as Microsoft SQL Server Integration Service
    Net FHIR API to map the resulting data set to one or more FHIR resources. ... Net Framework, Vonk FHIR Facade will require Windows or Azure App Service.
    https://customersurveyinfo.com

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  FHIR Standard Implementation  ·  Flag idea as inappropriate…  ·  Admin →
  8. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  FHIR Standard Implementation  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base