Skip to content

Commit cea3894

Browse files
authored
Merge pull request #102445 from CaitlinV39/master
Update fhir-faq.md
2 parents 73aeecf + 8511b85 commit cea3894

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

articles/healthcare-apis/fhir-faq.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,9 @@ ms.author: mihansen
1212

1313
# Frequently asked questions about the Azure API for FHIR
1414

15+
## What is FHIR?
16+
The Fast Healthcare Interoperability Resources (FHIR - Pronounced "fire") is an interoperability standard intended to enable the exchange of healthcare data between different health systems. This standard was developed by the HL7 organization and is being adopted by healthcare organizations around the world. The most current version of FHIR available is R4 (Release 4). The Azure API for FHIR supports R4 and also supports the previous version STU3 (Standard for Trial Use 3). For more information on FHIR, visit [HL7.org](http://hl7.org/fhir/summary.html).
17+
1518
## Is the data behind the FHIR APIs stored in Azure?
1619

1720
Yes, the data is stored in managed databases in Azure. The Azure API for FHIR does not provide direct access to the underlying data store.
@@ -32,6 +35,13 @@ The Azure API for FHIR is a hosted and managed version of the open-source Micros
3235

3336
When you're running FHIR Server for Azure, you have direct access to the underlying services. But you're also responsible for maintaining and updating the server and all required compliance work if you're storing PHI data.
3437

38+
From a development standpoint, every feature is deployed to the open-source Microsoft FHIR Server for Azure first. Once it has been validated in open-source, it will be released to the PaaS Azure API for FHIR solution. The time between the release in open-source and PaaS depends on the complexity of the feature and other roadmap priorities.
39+
40+
## What is SMART on FHIR?
41+
42+
SMART (Substitutable Medical Applications and Reusable Technology) on FHIR is a set of open specifications to integrate partner applications with FHIR Servers and other Health IT systems, such as Electronic Health Records and Health Information Exchanges. By creating a SMART on FHIR application, you can ensure that your application can be accessed and leveraged by a plethora of different systems.
43+
Authentication and Azure API for FHIR. To learn more about SMART, visit [SMART Health IT](https://smarthealthit.org/).
44+
3545
## Next steps
3646

3747
In this article, you've read some of the frequently asked questions about the Azure API for FHIR. Read about the supported features in FHIR Server for Azure:

0 commit comments

Comments
 (0)