2011 PCD Connectathon Lessons Learned

From IHE Wiki
Revision as of 16:20, 8 February 2011 by Jrhoads (talk | contribs) (start)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Ways to improve future PCD Connectathons

This is a collaborative page intended to capture every participant's insights on "lessons learned" from the 2011 PCD Connectathon. Please add your thoughts!

Increase realism of system performance under test

We need to "up the ante" on performing REALISTIC tests, and tests that are compatible with automated testing. In a realistic system:

  • Consumers shouldn't need to manually add parameters one by one - they should be preloaded with the full Rosetta repertoire of parameters. This is most practical when the system has the capability of importing a file of parameter definitions (what the system needs to know to make an appropriate display based on, for example, the contents of OBX-3 Observation identifier and OBX-6 Units).
  • No fair plugging in static contents where a real world system would be expected to generate appropriate values automatically. For example, NIST reports seeing some time stamps in messages that clearly were carried over from last year!

Improvements to the Connectathon Process

Improvements to the construction of particular tests