PHILIPS CMDK Care Management Development Kit

Speċifikazzjonijiet

• Product Name: CMDK Care Management Development Kit
• Verżjoni Rilaxx: 2.2

Karatteristiċi tal-Prodott

Data Dictionary
Custom Data Dictionary Management for Connected HISP.

Environment Selector

• Version-Specific HISP Management for CM-Ext Development.
• Sync Development Capabilities with HISP Environments.

Maniġer ta' Estensjoni

• Version and Release Control for HTML5 Enhancements.
• Rights management for extension provider.

Guardrails
Securing Philips HISP Elements from Unauthorized Customization.

Rules and Settings

General Settings Management.

Smartlink

• HISP Backend Event Interceptor and Database Interaction Development Support.
• Interoperability Development for HISP and External Systems.
• Low-Code Conditional Processing Flow Development.

UX Manager

• Custom User Interface Development with Frontend Logic.

Istruzzjonijiet għall-Użu tal-Prodott

Rekwiżiti ta' Installazzjoni
Ensure that all infrastructure requirements are met before proceeding with the installation process.

Appoġġ Tekniku
If you encounter any issues during usage, refer to the technical support guidelines provided in the manual.

Rekwiżiti ta' Sigurtà
Follow the security requirements outlined to ensure the safe usage of the product.

Użu Intenzjonat

• Care Management Development Kit (CMDK) is a standalone product that intends to provide an advanced integrated development environment (IDE) to technical users to extend and/or customize Tasy EMR functionalities, aiming on improving productivity and user engagement. CMDK allows the generation of pluggable extensions (CM-Ext) that are independent from Tasy EMR release cycle. The extensions are designed to be unpluggable, allowing the system to return to its original state.
• The scope of any extension to be developed using CMDK should meet Tasy EMR intended use, excluding all features related to its medical device functionalities.

Introduzzjoni
The following images summarize how CMDK is used and its main capabilities.

Karatteristiċi
This section describes the individual parts of the software product, also known as features, which combined form a comprehensive information system.

1. Infrastructure Requirements
   For more detailed requirements information refer to the CMDK Infrastructure Requirements Guide.
2. Rekwiżiti ta' Installazzjoni
   For more detailed requirements information refer to the CMDK Application Server Installation and CMDK Configuration Guide and the Database Configuration Guide.
3. Appoġġ Tekniku
   If you encounter difficulty using the product, contact the Philips technical support group that is serving your area. To obtain contact information for this group, contact your local Philips Representative.
4. Rekwiżiti ta' Sigurtà
   For more detailed information related to network safety, security and privacy refer to the Cyber Security Guide available on the Customer Portal and the European Standard Cyber Security for Consumer Internet of Things: Baseline Requirements document that can be found at https://www.etsi.org/.

Data Dictionary 

Custom Data Dictionary Management for Connected HISP
Allow the record management of custom data dictionary definitions for the connected HISP.
By providing the capability of adding, editing, or removing custom data dictionary components such as database tables, expressions, or PL/SQL objects, it allows the user to have the necessary elements that will interact with user interface or backend processing of connected HISP.

Environment Selector

Version-Specific HISP Management for CM-Ext Development

• Support management of possible HISP environments in specific versions, which will be the destination of the CM-Ext that is being developed.
• By having the possibility of multiple HISP versions for connection, it allows multiple environment options, therefore increasing HISP compatibility confidence and proper bug fixing environment, when necessary.

Sync Development Capabilities with HISP Environments

• Provide integration between the development capabilities and the selected HISP environment, retrieving and storing information accordingly.
• By retrieving and storing different data according to the connected system, it allows to develop in multiple versions of the destination HISP, where the screens and behavior reflect the version of the connected environment.

Maniġer ta' Estensjoni

Version and Release Control for HTML5 Enhancements

• Allow the management of different CM-Ext, including version and release control.
• Extension Manager is intended to provide the administrator with a tool to enhance the functionality of Tasy EMR while maintaining the integrity of the original product components. Each CM-Ext will comprise a set of components which combined deliver the proposed value when installed in the HISP.

Rights management for extension provider

• Provide extension activation rights control for Extension Provider.
• Allow the provider to define which Tasy customers should have access to install one extension developed by them. This functionality avoids non-authorized extension sharing and allows the providers to manage their extension installed base.

Guardrails

Securing Philips HISP Elements from Unauthorized Customization

• Customizing HISP elements which were defined by Philips as protected by guardrail rules is not allowed.
• There are elements within the HISP which Philips does not want to be customized for medical devices, patient safety, or strategic reasons. By having guardrail checks during the development process against online Philips rules, it will provide feedback to the user with the latest guardrail rules, not having to depend on a CMDK release update for the latest rules.

Rules and Settings

General Settings Management

• Allow defining general settings of the system, which are not user specific, or CM-Ext related.
• There are settings which should apply to user or CM-Ext, those are not function dependent and shall be managed only by the admin.

Smartlink

HISP Backend Event Interceptor and Database Interaction Development Support

• Support development of HISP backend event interceptors and HISP database interaction.
• By providing the capability to intercept specific events of the application such as saving records or button clicks, it allows the user to start and have the necessary inputs for conditional processing flow development for business rules need.

Interoperability Development for HISP and External Systems

• Support interoperability development between HISP and external systems/devices.
• By providing the capability to intercept inbound external system/device messages or sending outbound external system/device messages, it allows to start or finalize conditional processing flow development for interoperability need.

Low-Code Conditional Processing Flow Development

• Support development of conditional processing flows with low code approach.
• By providing creation of processing flows, with node options like parsing, condition handling or functional coding, it allows the user to develop necessary business rules either for interoperability or backend processing.

Ġestjoni tal-Utenti

Ġestjoni tal-Kont tal-Utent

• Allow creation and maintenance of admin and non-admin users.
• Each user needs to have their own account for security and traceability purposes. Only admin users shall have the option to create and maintain records of end-users, but they can also create other admin users if necessary.
• Admin users have the capability to enable and disable users as required. For example, if a user leaves the company, this would be an instance where the admin would have to disable the user account.

Secure Application Authentication with Self-Managed Passwords

• Provide complete authentication control of the application, with password self-management.
• The application can only be accessed with the right credentials. By providing password self-management for end-users, it provides less dependency on admin users and increased security, since there will be no need for password communication between admin  and user.
• When creating a user account, an activation link is sent to the user’s email address where they can choose their own password with no need for the admin user to be involved in the process.

Comprehensive Audit Trail for User Activities and System Events

• Maintain an audit trail of all user activities and provide traceability of system events to enable partners to track and review changes made to the system.
• It is required to ensure accountability and compliance with regulatory standards. Essentially whenever there is a change to the user account type (admin to member or vice-versa) or when a user account is enabled or disabled, a log is created to be able to track the changes.

Secure Management of Application Login Credentials

• Securely manage user login credentials for the application to maintain the security of the account and protect data.
• By having the ability to securely manage and update login credentials, users can ensure that their account is only accessible to authorized individuals.
• This gives the admin the ability to set after how many days the user password will expire and how many attempts of failed logins a user has to perform before being locked out of the system.

UX Manager

Custom User Interface Development with Frontend Logic

• Support development of new user interfaces or adapting existing user interfaces, with possibility of adding custom coding logic for frontend behavior.
• UX Manager is designed to provide flexibility on the customization while minimizing the risk of negatively impacting system functionality. By empowering users to create their own functions and customize existing structures, businesses can create software solutions that are tailored to their needs and workflows.

Abbreviations, Acronyms and Definitions 

Terminu Definizzjoni

• CM-ext Extensions provided by the CMDK
• Kit ta' Żvilupp tal-Ġestjoni tal-Kura tas-CMDK
• HISP Health Informatics Suite Product
• IDE Integrated Development Environment
• PL/SQL Procedural Language/Structured Query Language
• URS User Requirements Specification
• UX User experience

Glossarju tas-Simboli

Simbolu	Isem tas-Simbolu	Deskrizzjoni tas-simbolu
	Manifattur	Jindika l-isem u l-indirizz tal-manifattur
	Numru tal-katalogu	Indicates the manufacturer’s catalogue number so that the device can be identified

Care Management Development Kit (CMDK)

• Verżjoni 2.2
• Philips Medical Systems Nederland B.V. High Tech Campus 36  5656 AE Eindhoven The Netherlands
• 756030

• Id-drittijiet tal-awtur u d-drittijiet proprjetarji l-oħra kollha fi kwalunkwe softwer u dokumentazzjoni relatata (“Software”) disponibbli għalik huma esklussivament ta’ Philips jew tal-liċenzjaturi tagħha. L-ebda titolu jew sjieda fis-Software ma jingħata lilek. L-użu tas-Software huwa soġġett għall-kundizzjonijiet tal-liċenzja tal-utent finali kif disponibbli fuq talba.
• Published in Brazil
• 2025-08-15-en-us

FAQs

Dokumenti / Riżorsi

PHILIPS CMDK Care Management Development Kit [pdfManwal tal-Istruzzjonijiet CMDK 2.2, CMDK Care Management Development Kit, CMDK, Care Management Development Kit, Management Development Kit, Development Kit

Referenzi

• Manwal għall-Utent