1. Project Overview

A friend needed a clinic management system, so I simplified my original HIS system and deployed it for them. The results were quite good. I later considered selling it to other clinics, but the idea sounded better in theory than in practice. It was difficult to sell, the price was too low, and maintaining the business was troublesome. So I decided to open-source it instead, making it available to anyone who needs it rather than letting a good project go to waste.

Why is it calledLittle Apple Clinic SystemDoes this remind you of the famous song "Little Apple" that took the country by storm? Actually, the name wasn't chosen intentionally to reference the song. Initially, I wanted to name it after a fruit. I searched online for the healthiest fruit to eat, and the answer was apples. Since a clinic is essentially a small-scale hospital, I decided to call itLittle Apple Clinic SystemAnd later, I couldn't be bothered to change the name.

Our Mission: To bring positive changes to healthcare informatization through the power of open source.

Our Plans: In the short term, we will focus on completing the desktop version of the clinic system. Next, we may develop a Web version, followed by mobile features for both doctors and patients. Eventually, we may even build a medical cloud development platform.

2. Open Source License

Licensed under Apache-2.0

3. Screenshots

Interface Screenshots

Code Screenshots

4. Feature Overview

System Architecture Plan

5. Tech Stack

Compilation and Execution

Software Architecture

The software adopts a three-tier architecture consisting of a database, middleware, and client. The database server is isolated and is not directly exposed to the public internet. The system is a CS application, not a BS application. Whether to release a Web version in the future will depend on community feedback.

Directory Structure

DataBase					Database backup files
Docs						System documentation
MiniHISClient/				Client runtime environment
├── WinAssembly/			Stores UI assemblies
├── efwplusClient.exe		Client startup program*****
MiniHISServer/				Server runtime environment
├── Config/				    Stores configuration files
├── ModulePlugin/			Stores microservice plugins
├── ServerLog/				Stores middleware logs
├── efwplusBase.exe		    Server startup program*****
Setup                       Client installation package
SourceCode/						Source code
├── Component/				Third-party dependencies
├── Config/				    Configuration files
├── Launch/				Startup project
├── PluginClient/				Client plugin code
├── PluginServer/				Server plugin code
├── CHISAllClient.sln				Client source code solution
├── CHISAllService.sln				Server source code solution

Development Tools Preparation

1. Development Tools: Visual Studio 2019 or later
2. Runtime Environment: .Net FrameWork 4.6 (If the client runs on Windows XP, .Net FrameWork 4.0 can be used for compilation.)
3. Database: SqlServer2019 or later

Compile the code using VS

1. Clone the source code to your local machine
2. Database backup filesDataBase\MiniHIS.zip, extract the files and restore the database using a database management tool.
3. Open the server configuration fileEntLib.config, modify the database connection string.
4. Open each source code project separatelyCHISAllClient.slnandCHISAllService.sln and compile the projects.StartClientandStartServer
5. Run the server and client applications separatelyMiniHISServer\efwplusBase.exeandMiniHISClient\efwplusClient.exe
6. Login credentials: admin/1