A user who has completed the registration process, logged into Rekonnect, and has access to its features.

Definition: The highest privileged role within Rekonnect, with comprehensive access and management capabilities for the platform.

Permissions:

Definition: Individuals pivotal in managing relationships between MedTech companies and their customers, responsible for distributing product content.

Permissions:

Definition: Users with higher access levels responsible for managing customer users within the system and overseeing user interactions.

Permissions:

Definition: Users who have limited access to the system, primarily for accessing content and training materials.

Permissions:

The interface in Rekonnect that is visible to all user roles, displaying published content such as products, courses, documents, and more.

An interface only available to owners and administrators (not product users) that allows for the creation and distribution of materials like products and courses.

An interface within the Admin Portal that displays statistics, data, user engagement metrics, and more, available to administrators.

A navigation menu within the Admin Portal for administrators to access different content creation and management pages.

The menu is located in the top right corner of both the User Portal and Admin Portal, holding information related to the currently logged-in user profile.

A drop-down menu located in the top bar on both the User Portal and Admin Portal that changes the language setting of the user interface.

Profiles representing healthcare organizations or customers that use MedTech products and utilize Rekonnect for staff training and accessing product information.

Accounts for distributors responsible for managing relationships between MedTech companies and customers, and distributing product content.

Accounts group users together for more granular access control, allowing administrators to assign specific products and training materials to groups within a customer entity.

Managing different versions of products, training, courses, and documents through numbered iterations to ensure content quality, compliance, and integrity. Only one version can be published at a time, and previous versions are archived when new versions are published.

The different stages content can be in within the publishing workflow:

Creating: The initial stage where new products or training materials are developed.

Updating content that increments the version number minimally (e.g., from 1.1 to 1.2), typically for small changes or updates.

Updating content that increments the version number significantly (e.g., from 1.0 to 2.0), usually for major changes or overhauls.

Items or materials created and managed within Rekonnect, including product descriptions, documents, and associated training courses. Each product includes a unique name, description, Universal Device Identifier (UDI), and linked content.

Defined processes or methods within Rekonnect, associated with products and including relevant training materials and documents.

Structured training materials in Rekonnect, including self-study and teacher-led training, comprising multimedia content and quizzes designed to educate users about MedTech products and training.

Training modules are designed for users to complete independently at their own pace, with progress saved and tracked within the system.

Training sessions led by an instructor, scheduled within Rekonnect, where progress is not automatically tracked, but completion can be marked by trainers or administrators.

Digital files such as PDFs, images, and videos, uploaded and managed within Rekonnect, and linked to products or training from the edit screen.

The measurable element of courses that shows user engagement and completion status, displayed as percentages or states such as “In Progress” or “Completed.”

Tools within Rekonnect that allow users to provide feedback directly on products, training, and documents, including customizable forms with various input types and a messaging tool for communication with administrators.

Customizable forms designed by owners for users to provide feedback, including elements like free text, emojis, star ratings, single and multiple-choice selections, and grading scales.

Customizable questionnaires that can be sent via email to product users, linked to specific products or general topics, to gather user input and feedback.

Completed forms or surveys submitted by product users from the User Portal, accessible to administrators for review and action.

The ticketing system in Rekonnect where users can raise support issues related to products, managed by owner administrators through various workflow states.

Support issues raised by product users, containing details like product, priority, Adverse Event Reporting (AER) Code, subject, and description, used to track and resolve issues.

The process of handling and resolving support issues, involving states such as New, Open, Pending, On Hold, Solved, and Closed.

A code used to identify and report adverse events related to medical products or training within the support issue management system.

An area within an individual ticket where a product user and owner administrators can communicate via written text to collaboratively solve problems, including the ability to attach documents like screenshots.

Collaborative spaces within Rekonnect where users can engage in discussions, share files, and collaborate in real-time, are especially useful for clinical trials and MedTech product development.

A feature package that allows a subset of users to communicate via rich text chats with attachments in multiple threads and share files in multiple file shares.

A set of protocols and tools that allows different software applications to communicate with each other.

A feature package that logs and exports all Create, Read, Update, Delete (CRUD) operations on Products, training, Courses, Documents, Customers, Distributors, Support issues, and Users, including login and logout activities.

A cloud computing service created by Microsoft, used for hosting Rekonnect to ensure enhanced reliability, security, and scalability.

A feature that enables direct communication between end users (Product Users) and product developers, facilitating feedback and support without intermediaries.

Additional fields that can be added to entities like Customers, Distributors, Sales Companies, and Courses, supporting various data types such as text, numbers, dates, and select options.

An acronym for Create, Read, Update, Delete; refers to the basic operations of persistent storage in computing.

A feature package that enables the owner to receive feedback via forms or directed surveys from users.

Organizations such as clinics or hospitals that use MedTech products and utilize Rekonnect for staff training and accessing product information.

Individuals such as doctors and technicians who use MedTech products and benefit from the training materials provided through Rekonnect.

Refers to medical technology companies that develop products and use Rekonnect to manage and distribute training content to customers.

An architecture within Rekonnect that allows multiple owners to host their environments within the same application, each with customization options.

A library for ASP.NET developers used in Rekonnect to enable real-time web functionality, such as live online status indicators in Community Boards.

A software distribution model in which applications are hosted by a vendor or service provider (like Rekonnect) and made available to customers over the internet.

A feature package that allows the owner to receive and manage support issues from users within the platform.

A feature package that includes version-controlled courses linked from Products and Training.

An additional security layer requiring users to provide a code from a mobile authentication app or email in addition to their regular login credentials.

A unique product code for medical devices that aligns with Medical Device Regulation (MDR) standards, used within Rekonnect's product definitions.

The process where users are added to Rekonnect, receive invitations, and complete their registration to become active users.

Defined levels of access within Rekonnect, including Product User, Customer Administrator, Distributor Administrator, and Owner Administrator, each with specific permissions.