New Features in 1.1.0:

• Authentication without electronical health card: Fasttrack (Feature flagged)
• Manage multiple profiles (Feature flagged)
• Desktop Client

Prescriptions for medicines that are only available in pharmacies can be issued as electronic prescriptions (e-prescriptions resp. E-Rezepte) for people with public health insurance from 1 July 2021. The official gematik E-Rezept App (electronic prescription app) is available to receive and redeem prescriptions digitally. Anyone can download the app for free:

and login with the health card of the public health insurance. In July 2021, the e-prescription will start with a test phase, initially in the focus region Berlin-Brandenburg. The nationwide rollout will follow three month later in the fourth quarter.

The e-prescriptions are stored in the telematics infrastructure, for which gematik is responsible.

Visit our FAQ page for more information about the e-prescription.

For endusers and insurant:

Members of the health-industry with functional questions

IT specialists

You can find the privacy policy for the app at: https://www.das-e-rezept-fuer-deutschland.de/app/datenschutz

We plan to enable contribution to the E-Rezept App in the near future.

The E-Rezept App is licensed under the European Union Public Licence (EUPL); every use of the E-Rezept App Sourcecode must be in compliance with the EUPL.

You will find more details about the EUPL here: https://joinup.ec.europa.eu/collection/eupl

Unless required by applicable law or agreed to in writing, software distributed under the EUPL is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the EUPL for the specific language governing permissions and limitations under the License.

To get started, build one of the *Pu* variants. Currently, the Google and Huawei variants differ only in configuration. The code is identical. This is likely to change soon.

This repository is an Kotlin Multiplatform Project unifying the upcoming E-Rezept App for desktop and the Android App.

|-- android
|   `-- src
|       |-- androidTest
|       |-- debug
|       |-- main
|       |-- release
|       |-- sharedTest
|       `-- test
|-- common
|   `-- src
|       |-- androidMain
|       |-- androidTest
|       |-- commonMain
|       |-- commonTest
|       |-- desktopMain
|       `-- desktopTest
|-- desktop
|   `-- src
|       |-- jvmMain
|       `-- jvmTest
`-- plugins
    `-- dependencies

plugins/dependencies is a composed build required by any of the other modules (android, common and desktop) managing the dependencies in one place.

The gradle.properties file contains all pre-defined properties required to communicate with the FD (FachDienst), IDP (IDentity Provider) and the pharmacy lookup service. Unfortunately the actual values are not meant to be public.

To build the Android App choose one variant (e.g. gradle :android:assembleGooglePuExternalDebug -Pbuildkonfig.flavor=googlePuExternal):

gradle :android:assemble(Google|Huawei)Pu(External|Internal)(Debug|Release) -Pbuildkonfig.flavor=(google|huawei)Pu(External|Internal)

Note: Currently the android build variant is derived from the buildkonfig.flavor property.

The resulting .apk can be found in e.g. android/build/outputs/apk/googlePuExternal/debug/.

To build a fat JAR run:

gradle :desktop:packageUberJarForCurrentOS -Pbuildkonfig.flavor=desktopPu(External|Internal)

Java 15 is required to execute the JAR located in desktop/build/compose/jars/.

• E-Rezept iOS implementation
• Reference implementation of the IDP (IDentity Provider)
• Reference implementation of the FD (FachDienst)