Skip to content

Documents & infrastructure

CareOn SAP DMS

Secure document access. Clear storage responsibilities.

The SAP SFTP DMS Service connects clinical document repositories with authorised applications. Its SFTP bridge exposes connected storage without maintaining a separate, persistent local archive of patient documents.

Medicine. Information. Technology.

Context

At a glance.

01

Secure transfer

SFTP carries file operations over an authenticated, encrypted SSH connection. Access is limited by the account and its permissions.

02

Transient access

Documents remain in the connected repository. Reading a file through the bridge does not create an independent archive on the bridge.

03

Clear responsibilities

Document creation and downstream processing belong to the relevant applications. Transfer infrastructure and its dependencies have their own operational responsibilities.

How it works

Follow the workflow.

  1. Request a document

    An authorised application requests a document using its reference and permitted path.

  2. Access the repository

    The bridge reads the requested document from connected upstream storage.

  3. Transfer the contents

    Document bytes pass through the SFTP connection to the requesting application. The source document remains in its repository.

  4. Process in the application

    The receiving system displays, attaches or ingests the document. A successful transfer does not by itself confirm that this application step succeeded.

Conceptual diagram · not live data

Service architecture

From document access to recovery.

What “transient” means

The bridge provides access to documents stored elsewhere; it is not a second patient-document archive. A directory visible through SFTP can represent mounted storage rather than files on the bridge’s own system disk.

This describes patient-document persistence, not the absence of all server data. Configuration, access records and any implementation-specific buffering or temporary files must be managed separately. A read does not imply deletion or expiry of the original document.

Connecting clinical and business workflows

Clinical systems can make reports and referral documents available to SAP-integrated applications and authorised downstream services. Each integration needs an agreed document scope, access permissions and a responsible application owner.

Document generation, transfer, archive ingestion and attachment processing are distinct steps. When a document is missing downstream, first establish that it was created and stored, then trace access, transfer and application processing.

Access and service operations

Service accounts and SSH public keys support controlled machine-to-machine access. The server’s host key identifies the endpoint; a client key authenticates an account. Authentication does not automatically authorise access to every document.

The infrastructure service covers connectivity, access control, directory integrity and operational monitoring within the agreed service scope. Monitoring should distinguish a reachable server from a working storage connection and successful document retrieval. Availability and response commitments belong in the applicable service agreement.

Backup and recovery follow the storage

Recovering the bridge configuration and recovering patient documents are separate tasks. A backup of the bridge virtual machine does not automatically include externally mounted document storage.

Document protection must be established for the actual backing storage: identify its owner, confirm backup inclusions and exclusions, agree retention and recovery objectives, and verify restoration. Any retained downstream copies have their own protection requirements.

Neither a successful transfer nor a successful virtual-machine backup establishes end-to-end recoverability. A meaningful recovery check restores a document and confirms that the intended application can retrieve it.

Explore the details

The original article.

The original service-desk article is preserved below. The editorial context above explains the service; statements in the source reflect its publication date.

Source updated: · Mirrored:

Read original article Content & documentation

SAP SFTP DMS Service

Service Overview

The SAP SFTP Document Management System (DMS) provides secure file transfer and document storage infrastructure for SAP-integrated applications across the organization.

Service Details

  • Protocol: SFTP (Secure File Transfer Protocol)
  • Primary Function: Centralized document storage and retrieval for SAP and integrated healthcare systems

Service Scope

Our Team Is Responsible For:

  • SFTP/DMS server availability and uptime
  • Server infrastructure maintenance
  • Network connectivity to the server
  • Directory structure integrity
  • User authentication and access control

Outside Our Scope:

  • Individual application integrations
  • Specific document link generation
  • Application-level file processing
  • Content validation or formatting
  • End-user application troubleshooting

Support Requirements

When reporting issues, please provide:

  • Connection error messages (if applicable)
  • Specific file paths or links in question
  • Timestamp of the issue
  • Affected user account or application

SLA

Standard infrastructure support SLA applies. Server availability is monitored 24/7.

← All companies & solutions
eMedys AG

Company and product information
Source mirror dated · Content responsibility: eMedys AG

eMedys overview ↗