- Profiling (documentation that focuses on a use-case, specifying the standards to use and the constraints on the standards) is an International need that IHE and Continua are addressing:
- IHE is increasingly adopted world-wide (see Where in the World is XDS and CDA implemented)
- In the context of the stage 1 choices there is consistency in many area. Going forward, in Stage 2, IHE is consistent with DIRECT and can bring the most robust and already implemented solution that address the needed use cases deployed approach to point-to-point, HIE and NHIN Exchange.
- Use-cases are submitted from any interested party. These must be justified and go through a priortization process to pick the few that will be worked on
- The use-cases are then decomposed into the abstract actors and abstract transactions, and available standards are identified. This results in the Public Comment
- After Public Comment the Profile is further developed into the technical specification that goes out for Trial Implementation.
- Trial Implementations are used by developers that bring their solutions to the Connectathon. This tests both the software implementation, which must show interoperability with two other independently implemented solutions. The result tends to also uncover issues with the Profile text, what IHE calls a Change Proposal. Once a Profile has been proven at Connectathon, then it gets frozen in the Final Text phase. No breaking changes are allowed once a Profile enters Final Text. This is also when the Profile gets translated into the formal documentation publication form of the Technical Framework.
- Those products that pass Connectathon are allowed into some form of trade show demonstration, with HIMSS being the big one for the IHE ITI committee. These demonstrations leverage the capabilities provided by the Profiles implemented in as close to a real world setting as possible.
- Products are expected to publish an IHE Integration Profile as a statement of their products capabilities. This is a binding statement that they are expected to back through fixing any issues of non-conformance found.
- The result of this is that products are available in the market space that are easy to identify their capabilities through the IHE Integration Statement, and have proven them-selves at Connectathon
- Ultimately the result for everyone is better Interoperability. The Providers participate through offering up problems to solve, and by agreeing that they want the solutions. The Vendors participate through working through a solution and implementing it because they have assurances that the solution is desired. Both sides win.
- e-mail Push of a document without metadata
- e-mail Push of documents with metadata to enable automated processing (XDM)
- Web-Services Push of documents with metadata between automated systems (XDR)
- A Community Exchange using Publication and Discover/Retrieve (XDS)
- Multiple Communities Exchanging using Discover and Retrieve (could be XDS or proprietary source)
This was a fun experience and I really enjoyed the other presentations. I encourage everyone to review all the presentations and papers that are now published on the HL7 site.
thanks for your sharing I am your huge fans
ReplyDelete