Talk:Integration Statement Registry

Search Use Cases

Customer Shopping List

A customer is interested in finding a system with a particular combination of Profiles and Actors.

They could select those search terms (radio boxes?) and get a list of systems (vendor/product/version) that support thosee Profiles/Actors

Might be useful to choose if the search should return systems that meet MOST of the specs, or perhaps combinations of systems that together can meet the spec.

Customer Profile Evaluation

A customer wants to know if a profile is "ripe" yet. They are thinking of planning to deploy it.

They want to select a profile and get a list of systems for each actor so they can make sure there is at least one of everything and possibly see if some of the actors are supported/supportable on any of their current systems.

Domain Committee Profile Evaluation

A domain committee wants to evaluate penetration of some profiles in the market place. Is the profile (or actor) growing, stagnating, what phase of adoption they are at, or if they haven’t been picked up at all

Want to dump the number of reported implementations of each actor in a profile at one year after publication, two years, three years, etc.

Data Entry Use Cases

Web Entry

Vendors could manually enter the Integration Statement details for their products into a page on the registry using company managed IDs. They would be motivated to do so if customers were using it as a catalog of sorts.

XML Submission

It has been suggested that if IHE drafted an XML schema for integration statements, it would make it much easier to submit and work with this information. A style sheet for rendering them in PDFs would event let the XML file do double duty.