Skip to main content
» Home Page

gazelle banner

Menu
  • Home
  • Connectathon
    • NA Connectathon 2024
    • 2024 IHE Connectathon in Trieste
    • About the connectathon
    • Connectathon Results
    • Monitors
    • FAQ
    • Past connectathons
  • Tools
    • Index to all IHE Test Tools
    • Gazelle tools & user guides
    • Preparatory test cases
    • Reporting an issue in Gazelle
    • Bringing Gazelle in-house
  • Training
    • Index to trainings
    • Upcoming events
  • Gazelle Developers
    • Gazelle Developers Guide
    • Crowdin
    • Intellij Idea
    • Jenkins
    • Jira
    • Nagios
    • Nexus
    • SCM
    • Sonar
    • Testlink
  • Blog
  • Archives
    • Deprecated projects
    • Deprecated documentation
    • Past connectathons
  • Contact us

You are here

Home » Gazelle developers guide » Gazelle style guidelines

Gazelle style guidelines

Complete documentation

 

‹ Web service for validation up Guidelines for developing new Gazelle tools ›
  • Printer-friendly version
303 days since IHE 2024 Connectathon in Oak Brook.

Search form

Gazelle developers guide

  • Calibration tests with SoapUI
  • Development support tools (tips for Drupal, Eclipse, Jboss, Linux and so on)
  • Development tips (Use of common-module, calls to API, knowledge sharing and so on)
  • Gazelle style guidelines
  • Guidelines for developing new Gazelle tools
  • Installing Syslog tools (MIR)
  • Simulator Developer Guide (use of modules shared by simulators)
  • Test Management (system testing - automated)

Quick links

  • IHE Technical Framework
  • IHE Product Registry
  • Connectathon Results
  • Gazelle for Europe
  • Gazelle for NA
  • Validation Portal (EVSClient)
  • IHE Europe
  • IHE USA
  • IHE Services
  • More links

User login

What is OpenID?
  • Log in using OpenID
  • Cancel OpenID login
  • Request new password

Credits | License | Contact us | References

2010-2018 © IHE International