Tools

From HL7-Europe Wiki
Jump to: navigation, search

Tools Index

This is a (nascent) list of available tools

Tool Short Author
EHR-S FM FP Designer Tool  EHR-S FM Profiler Giorgio Cangioli
ART-DECOR®  HL7 Templates, Value Sets and more dr Kai U. Heitmann

Characteristics

The following list represents the currently used characteristics for the tool descriptions

Categories and Classes

Categories and Classes

  • Business/Clinical requirements specification
    • business process / use case modeling
    • data set / domain modeling
    • Requirements management systems
    • Model registry/repository
  • Base Standard specification
    • Standards registry/repositories
    • Standard development
    • Publication tool
  • Profile (template) specification
    • Profiles registry/repositories
    • Profile development
  • Product development support
    • Code generators
    • Test data generators
    • Help desk
    • Examples libraries
    • Software libraries
    • Reference implementations
  • Deployment support
    • Issue tracker / Tickets management
    • Help desk
    • Terminology services
    • Standard/profile mapping systems
  • Procurement Support
    • Requirements management systems
  • Maintenance support
    • Issue tracker / Tickets management
  • Verification and Validation
    • Test management tools
    • Conformance testers
    • Interoperability validators
    • Simulators/Stubs
    • Test Data generators
    • Network sniffers
    • Support Tools

Use

  • remote (e.g. web)
  • local
  • both

Distribution

  • On Premise
  • PaaS - Platform as a Service
  • SaaS - Software as a Service
  • BaaS - Backend as a Service

Tool Access

  • Free: Free use of a testing tool, either over the network or free download and installation.
  • Commercial: A testing tool can be accessed under commercial conditions set by the entity that developed or owns the tool.
  • Member restricted access: The testing tool can be accessed under condition of membership in an organization that owns/controls the tool.
  • Combined access: There are examples of testing software that is free to use but requires run time environment that is proprietary and subject to commercial conditions

Source Code

  • Open source: The source code of a testing tool is freely available.
  • Not open: The source code is not freely available.
  • Partly open: The source of the testing software is freely available but requires run time support that may not be free.