hm_editor

HmEditor MCP server exposes a web-based medical electronic record editor built on CKEditor4 with integrated AI capabilities. The server is implemented in Node.js and can be started directly with a Node runtime. Once running, you can load the editor into a web page via the provided SDK loader, allowing you to render the editor UI, bind to patient record templates, and interact with AI-assisted features such as content suggestions, drafting, and data binding to EMR systems. Typical usage involves hosting the editor in a frontend application and using the SDK to initialize the editor with a container element and a backend host URL. The server also provides an admin/demo interface when deployed with the Docker setup, enabling quick demonstrations of the editor and management UI. The included CDN script demonstrates how to load the editor asynchronously and configure a host from which the editor resources are served.

Capabilities include: - Rich data元 components (text, date, single/multiple choice, dropdowns, tables, images, and diagrams) - AI service integration for drafting and revision workflows - Configurable templates to support multiple medical record templates - Front-end integration via HMEditorLoader with a simple async initialize pattern - Localized and front-end ready, pure front-end runtime for easy integration across platforms.

Prerequisites:

• Node.js 12.x or newer (as indicated by the project badges)
• npm (comes with Node.js) or yarn
• Optional: Docker and docker-compose for Docker-based deployment

Installation steps:

1. Clone the repository or obtain the source code for hm_editor.
2. Install dependencies: npm install
3. Build/prepare for release (if applicable): grunt release
4. Start the server locally (development): node index.js (Alternatively, use nodemon for automatic restarts during development: nodemon index.js)

Docker deployment (recommended for quick start):

1. Ensure Docker and docker-compose are installed.
2. Use a docker-compose YAML provided by the project (docker-compose.prod.yml or similar).
3. Start the services: docker-compose -f /path/to/docker-compose.prod.yml up -d

Notes:

• The editor is designed to run as a frontend/backend pair. The Node server serves the editor resources and API endpoints consumed by the frontend SDK.
• If you upgrade Node versions, ensure dependencies (grunt, etc.) are compatible.

Tips and notes:

• This editor uses CKEditor4 under the hood with a custom AI integration; ensure your AI service endpoints are reachable and configured as needed.
• If you run behind a reverse proxy, configure proper TLS termination and WebSocket support if used by the frontend.
• For production, prefer Docker deployment or a properly orchestrated Node process manager (PM2, nodemon in production is not recommended).
• Environment variables: PORT should be set if you override the default port; consider exposing additional environment variables for API endpoints or feature toggles as required by your EMR integration.
• Check official docs and demo interfaces to verify the editor's APIs and initialization patterns before integrating into a production EMR workflow.