Implementation Guide
TIFlow - Verordnungen für Arzneimittel
Version 2.0.0-ballot.2 - ballot

## Example Bundle: Beispiel Accept-Bundle

Profile: GEM ERP PR Bundle OP Accept version: 2.0.0-ballot.2

Bundle Bundle-AcceptOperation of type collection

Entry 1 - fullUrl = https://erp-ref.zentral.erp.splitdns.ti-dienste.de/Task/d70932d1-9e1c-483c-b2d4-b7dced09b35e

Resso}:

> Profile: Task für E-Rezept version: 2.0.0-ballot.2

> Tag:

> TI Flow Type: CodeSystem der Flowtypes in TIFlow Anwendungen: 160 (Flowtype für Apothekenpflichtige Arzneimittel)

> TI Flow AcceptDate: 2028-10-01

> TI Flow ExpiryDate: 2028-10-01

> identifier: `https://gematik.de/fhir/erp/NamingSystem/GEM_ERP_NS_PrescriptionId`/160.000.033.491.280.78, `https://gematik.de/fhir/erp/NamingSystem/GEM_ERP_NS_AccessCode`/777bea0e13cc9c42ceec14aec3ddee2263325dc2c6c699db115f58fe423607ea

> status: In Progress

> intent: Order

> for: Identifier: NamingSystemKVID/X123456789

> authoredOn: 2028-10-01 15:29:00+0000

> lastModified: 2028-10-01 16:44:00+0000

> ### Inputs

> - | Type | Value[x]
> * | Health Care Provider Prescription | Binary/PrescriptionBinary

Entry 2 - fullUrl = https://erp-ref.zentral.erp.splitdns.ti-dienste.de/Binary/PrescriptionBinaryWithMeta

Resso}:

> Profile: GEM ERP PR Binary

> contentType: application/pkcs7-mime

> data: `dGhpcyBibG9iIGlzIHNuaXBwZWQ=`