The Apotti ecosystem

The Apotti Online Sandbox is a tool for interface testing as well as technical software testing and practice. We recommend the FHIR (Fast Healthcare Interoperability Resources) interface technology.

More background information is available at the end of these instructions.

In these instructions we presume that you are already familiar with FHIR interfaces and SMART Launch. A good source material is the https://fhir.epic.com/ page and especially the Documentation tab.

Please also note, that we give instructions to the so-called standalone launch, i.e., starting your app without access to the Apotti end user interface (Hyperdrive). Access to this environment is limited by restrictions set by Epic. Apotti will help you in a separate phase when it becomes topical to embed your application into the end user interface or to the Maisa client portal.

• Get a Client ID:
  • You can get a Client ID from fhir.epic.com
  • Log in to fhir.epic.com
  • Select the “Build Apps” tab

 

• Create App.
• Give the application the needed FHIR/CDS Hooks recourses. If you know exactly what you need, select the appropriate ones. If you aren’t sure, select all.

 

• Click the ”Save & Ready for Sandbox” button in the bottom of the screen and the service generates production and non-production Client IDs.

 

• If you wish, you can test the non-production Client ID after a technical lag against the Epic Sandbox environment. Please note, that the Epic Sandbox contains American model data that differs from the Finnish data provided by Apotti.
• When you wish to enter the Apotti Sandbox (Apotti Online Sandbox), click the ”Save & Ready for Sandbox” button and forward the “non-production” Client ID to Apotti to ekosysteemi@apotti.fi. Please note, that your application’s Client ID rights will be locked at this point, and later adjustments require that you create a new app.
• Request Apotti to download a Client ID to the Online Sandbox.
  • Send an e-mail message titled “Requesting a Client ID download to the Apotti Online Sandbox” to ekosysteemi@apotti.fi.
  • Apotti will download the Client ID to its own Sandbox environment (Apotti Online Sandbox). The Client ID will take a day to activate, often even less. You will receive an activation notice by e-mail.
  • At a later stage you can take advantage of the Epic App Market (vendorservices.epic.com) according to the service price level of your choosing.
• Acquire a provider or patient User ID.
  • Request for generic provider or patient/client IDs: ekosysteemi@apotti.fi.

Your application can then start using the Apotti Online Sandbox FHIR interfaces. After this our technological, content-based and functional network cooperation will deepen phase by phase.

Conduct Guidelines

• Do not cause unnecessary harm to the Sandbox database even though it is reset to its original state regularly.
• Do not cause denial of service attacks against the Sandbox.
• Do not violate the immaterial rights of Apotti, Epic or any other partners.

Close

Epic is the software system at the core of Apotti and therefore the Client ID is retrieved from fhir.epic.com. FHIR practice helps ecosystem partners reach the global Epic market.

Apotti Online Sandbox is an Apotti system containing artificial Finnish patient and client test data and therefore it’s possible to experiment and test without compromising patient and client safety.

The Apotti Online Sandbox encompasses the entire social care and health care sector covering also social welfare services and primary health care in addition to specialised medical care.

• Sandbox Interconnect IP: https://gw.apottiekosysteemi.fi/Interconnect-FHIR-EKO01/api/FHIR/R4/metadata
• General content and reset practices and policies of the Sandbox database
  • Content-wise the Sandbox is a copy of the Apotti training environment, and it does not contain real patient or client data or events.
  • Further information: ekosysteemi@apotti.fi

• Available FHIR recourses and Finnish profiles pinpointed from the data
  • Epic supported resources: fhir.epic.com
  • Finnish profiles: fhir.fi
  • In addition, Epic’s Web Services and traditional HL7 V2 and CDA

 

Different launch options

• • Standalone launch (see instruction higher above)
    • The application will launch outside of the Apotti end user interface.
  • Professional EHR Launch – Hyperspace/Hyperdrive
    • The application is embedded in the end user interface where it will get the intended context when launched.
    • Apotti offers a model application of this kind (browser interface JS/Angular, server Java/Spring).
    • The Apotti register lines restrict the EHR Launch in the Uusimaa region at the moment. For instance, a specialised medical care provider (HUS) cannot search their patient’s primary care information in the Apotti system.
    • Epic’s IPR restricts the access to Hyperspace.
  • Patient Facing Launch of patient/client
    • The application has been embedded in to the Maisa (MyChart) client portal, with DVV (Digital and Population Data Services Agency) authentication.
    • Server to server.
    • More detailed information about this will be provided later.

Close