Daten schnell und zuverlässig integrieren mit ViREQ / conGATE auf Basis von Mirth Connect. 1 Substitutable Medical Applications and Reusable Technologies (SMART on FHIR) ist. 2 › Learn › Azure › Azure-API für FHIR. 3 Ziel des Smart App Launch ist es, ein Zugangstoken von einem OAuth kompatiblen Autorisierungsserver zu erhalten, mittels dessen eine FHIR Restful API. 4 Next steps Substitutable Medical Applications and Reusable Technologies (SMART on FHIR) is a healthcare standard through which applications can access clinical information through a data store. It adds a security layer based on open standards including OAuth2 and OpenID Connect, to FHIR interfaces to enable integration with EHR systems. 5 SMART on FHIR is a set of open specifications to integrate partner applications with FHIR servers and electronic medical records systems that have FHIR interfaces. One of the main purposes of the specifications is to describe how an application should discover authentication endpoints for a FHIR server and start an authentication sequence. 6 SMART defines how third-party apps launch within an EHR, how to determine which EHR user is interacting with the app, and what patient’s data is being accessed. What is it like to implement a SMART on FHIR app? The process of implementation happens in the following steps: The specification is developed. 7 Today it is known as ‘SMART on FHIR’ or SMART (the term that will generally be used here and will subsequently refer to SMART on FHIR rather than the original SMART API). The project team often uses ‘SMART on FHIR API’ to refer to it. SMART is now widely adopted by the same major EHR vendors that objected to the original SMART technology. 8 SMART (Substitutable Medical Applications and Reusable Technologies) is a standards-based, interoperable apps platform for electronic health records. SMART was originally developed—before FHIR was ever ignited—by the Harvard Medical School and Boston Children’s Hospital in 9 SMART on FHIR defined a way for health apps to connect to EHR systems with appropriate security guarantees (Box 2). In addition to FHIR models and API, components included authorization, authentication, and UI integration (Table 1). Box 2: SMART on FHIR technology components Table 1: SMART on FHIR vs. FHIR Alone Open in new tab Table 1. fhir vs hl7 10