Medtech Partner Program

Innovation is one of the cornerstones of Medtech's success over the last twenty five years. Medtech invests and maintains an active research and development program to drive continuous improvements in our existing products as well as developing new products to meet the needs of our customers.

Medtech also has an active partner program, designed to support independent software vendors who develop and market complementary software products that deliver incremental value to our customers when integrated with Medtech products.

Benefits

As an independent software vendor, you may be faced with numerous challenges ranging from struggling to accelerate time-to-market, sustaining the costs of doing business, economically distributing your product to your target customers, and establishing and maintaining a technical support helpdesk to name a few.

Time and money spent on these challenges, is time and money not being invested in your core product features and functionality. Such efforts can severely reduce your development productivity, losing you valuable market opportunity and product revenue.

The Medtech ISV Partner Program offers independent software vendors (ISVs) valuable tools and resources designed to help deliver products with a strong competitive edge by integrating and embedding complementary products with Medtech software.

Key benefits for ISV partners :

• accelerate time-to-market
• lower overall cost of doing business
• generate revenue quickly and profitably
• access to Medtech product development and technical resources
• technical support
• compatibility testing and product certification
• marketing and sales support

Integration of complementary third party products with Medtech32 software

How does Medtech decide which products to integrate?

Usability, reliability, performance, on-going maintenance and technical support are among the main criteria for customers choosing Medtech products. Hence, Medtech evaluates the suitability of integrating any complementary third party products along the following key principles:

1. Relevance to Medtech Customers

The product wishing to integrate must deliver incremental value to Medtech customers when integrated with Medtech32 software. The actual activation of any third party product is on an opt-in basis initiated by the Medtech customer.

2. Relevance of Medtech Applications

The Medtech32 application is a functionally rich application and should not be viewed as a data repository for third party applications. Integration of any third party product should utilise all existing Medtech32 functionality and should not diminish, disable or replace any existing Medtech32 functionality.

Example 1: A third party application that integrates with Medtech32 which needs to raise an invoice, should call (use) the invoice module in Medtech32 to create the invoice, as opposed to re-writing an invoicing module.

Example 2: A third party application that integrates with Medtech32 which needs to generate a prescription, should call (use) the prescribing module in Medtech32 to generate the prescription.

3. Completeness of Patient Records in Medtech32 Database

The product wishing to integrate must follow Medtech’s guidelines and use the interfaces provided to write back any new data created by the third party application into the Medtech32 database.

Example 1: A decision support tool that creates new data should write this data back (and the completed assessment) back into the respective areas in the Medtech32 database.

Example 2: A third party application that creates a referral document must save a copy of the referral in the correct place in the Medtech32 database.

4. Usability and Workflow

The product wishing to integrate must demonstrate that integration of the third party product does not adversely impact on the usability and/or the workflow of the Medtech products.

5. System Performance

The product wishing to integrate must demonstrate that integration of the third party product, does not adversely impact the performance of the Medtech products.

6. System Reliability

The product wishing to integrate must demonstrate that integration and/or embedding of the third party product, does not adversely impact the reliability of the Medtech32 product.

The third party product should not cause:

• Medtech32 application to crash
• Medtech32 database corruptions
• Medtech32 installation errors

7. System Security

The product wishing to integrate must demonstrate that integration and/or embedding of the third party product, does not:

• introduce any vulnerabilities
• compromise Medtech32 application security
• compromise Medtech32 usernames and passwords
• disable antivirus software and/or security firewalls
• compromise the security of the system environment including, but not limited to, servers, desktops, laptops, network, fileservers and databases

8. Data Privacy

The product wishing to integrate must demonstrate that integration and/or embedding of the third party product, does not:

• compromise the privacy and confidentiality of practice data
• compromise the privacy and confidentiality of patient data

9. Compatibility with Medtech

The product wishing to integrate must demonstrate compatibility with Medtech32 and any dependent components required for the proper functioning of Medtech32.

Potential areas of compatibility are:

• Use of same version of operating system used by Medtech32
• Use of same version of browser supported by Medtech32
• Use of same version of other products (e.g. Microsoft Word, Microsoft Office)
• Use of installed components such as DLL’s
• Use of Web Server used by Medtech32
• Use of the same technical frameworks (e.g. .NET)

10. Compatibility with existing third party products

The product wishing to integrate must demonstrate compatibility with existing third party products and any dependent components required for the proper functioning of the existing third party product.

The product wishing to integrate must not interfere with the proper functioning of existing third party products.