Documentation and scripts to simplify the installation and maintenance of an Orthanc based PACS Imaging Server for the orthodontic practice.
Explore the docs »

Report Bug · Request Feature

The project is currently not released yet. You can find current development in the develop branch.

• The Name Ovena
• About The Project
  • Built With
• Getting Started
• Roadmap
• Contributing
• License
• Contact
• Acknowledgements

Ovena comes from the acronym for Open-ortho Vendor Neutral Archive, which technically should be OVNA. However we selected to include the extra 'e' of 'Vendor' because the name flows better and also because it so happens that ovena means door in finnish. It is actually the essive case of ovi door, which translates to "as a door". And indeed, the PACS, in the medical practice, acts as a door, a portal through which images can move between different systems.

As more and more devices adopt and implement the ability to upload or download images in DICOM over the network, it is becoming possible for the orthodontic practice to gain full control over their patients data: all that is missing is a place to put and get all these images. That's where DICOM imaging server (PACS) come in to play.

It would be advantageous for every orthodontic practice to have a access to a DICOM PACS. Unfortunately, most commercial solutions are designed for large institutions and frequently not affordable for smaller orthodontic practices.

The purpose of this project is to provide:

1. a low cost way to set up a DICOM imaging server in the orthodontic practice;
2. demonstrate that a large and expensive DICOM PACS server is not required for smaller medical practices (like the orthodontic one).

It is really not that hard to set up a DICOM PACS server, and it also doesn't require a lot of hardware resources. There are, however, quite a few steps involved, and then there is maintenance. We want to simplify this as much as possible, and show anyone interest how to do it. Only with widespread adoption of DICOM servers will full and open interoperability become a reality

What you will find here:

• documentation for setting up an imaging server using the open source Orthanc PACS server, a PostgreSQL database and an NGINX server, all in docker containers.
• scripts and other tools for maintaining the services.

You may suggest changes by forking this repo and creating a pull request or opening an issue. Thanks to all the people have have contributed to this project!

A list of commonly used resources that we find helpful are listed in the acknowledgements.

• Orthanc
• PostgreSQL
• Docker
• nginx

Full documentation is in the gh-pages branch, and is accessible here.

1. Edit the Makefile and check that variables are OK.

2. Generate a .env file from dot-env.

3. Run

   make all make deploy

See the open issues for a list of proposed features (and known issues).

Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are greatly appreciated.

1. Fork the Project
2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
3. Commit your Changes (git commit -m 'Add some AmazingFeature')
4. Push to the Branch (git push origin feature/AmazingFeature)
5. Open a Pull Request

Distributed under the MIT License. See LICENSE for more information.

Toni Magni- @zgypa - [email protected]

Project Link: https://github.com/open-ortho/ovena

• DICOM
• American Dental Association Standards Committee for Dental Informatics