| HTML |
|---|
<div class="container"> <div class="row"> <div class="col-md-15 feature-box"> <a href="/display/CRR" data-toggle="tooltip" title="Clinical Requirements"><img src="/download/attachments/18743297/businessclinical_requirements.png?version=1&modificationDate=14745741187501474574119327&api=v2" class="feature-icon"></a> <div class="feature-description"> <h2<p><span data-togglestyle="tooltip" title="Clinical Context, Need and Requirements" >Clinical Requirements</h2> <p>Clinical Context, Clinician Expression of Need and Requirements and morefont-weight:bold;color:#e02e3b;">Clinical Requirements</span> describe the information and workflow needs of the clinician for a specific clinical context and clinical data exchange. Using the clinical Interoperability Principles as a guide, a set of requirements expressed in the clinician's voice will provide the foundation for a well-designed interoperability solution.</p> <ul class="guides-list" style="display:none;"> <li><a href="/display/IH/New+Space+Request">Request a new Clinical Requirement Space</a></li> <li style="display:none;"><a href="">Alberta Immunization</a></li> </ul> </div> </div> <div class="col-md-15 feature-box"> <a href="/display/BRR" class="centered"><img src="/download/attachments/18743297/clinicalbusiness_requirements.png?version=1&modificationDate=14745741193271474574118750&api=v2" class="feature-icon"></a> <div class="feature-description"> <h2<p><span data-toggle="tooltip" title="Business Requirements">Business Requirements</h2> <p>Usestyle="font-weight:bold;color:#e02e3b;">Business Requirements</span> are derived from clinical requirements and provide a full picture of the solution that needs to be developed. Use cases, business rules and guidance suggestedare used rulesto basedfully onoutline the clinicalsolution requirementsdesign.</p> <ul class="guides-list" style="display:none;"> <li><a href="">Business Requirements</a></li> <li><a href="">Xyz Lorem Ipsum</a></li> <li><a href="">Request for new Space</a></li> </ul> </div> </div> <div class="col-md-15 feature-box"> <a href="/display/STSS" class="centered" data-toggle="tooltip" title="Standards Selection"><img src="/download/attachments/20906479/ST3048882/standards_selection.png?version=1&modificationDate=14740561364131473884765673&api=v2" class="feature-icon"></a> <div class="feature-description"> <h2 data-toggle="tooltip" title="Standards">Standards</h2> <p>Access pan Canadian Standards and learn and implementation guidance.</p> <p><span style="font-weight:bold;color:#e02e3b;">Standards Selection</span> refers to the process that has been developed to help guide teams through the selection of terminology and messaging standards. Using the line of inquiry and considerations in the forms provided, implementation teams may assess the standards available and determine the best option for the point in time. The process also provides an opportunity for the InfoCentral community to share successful implementation projects, promoting standardization through reuse.</p> <ul class="guides-list" style="display:none;"> <li><a href="">Latest Standards Release</a></li> <li><a href="/display/SSG">Terminology>Selection Subsets<Guidance</a></li> <li><a href="">Previous versions of pan Canadian Messaging Standards</a></li> /display/SSG/Appendix+A+-+Standards+Assessment+-+template">Assessment template</a></li> <li><a href="/display/GR">Guide Registry</a></li> <li><a href="/display/SSG/Appendix+B+-+Selection+Guide+-+template">Guide template</a></li> </ul> </div> </div> <div class="col-md-15 feature-box"> <a href="/display/SSST" class="centered" data-toggle="tooltip" title="Standards Selection"><img src="/download/attachments/3048882/standards_selection.png20906479/ST?version=1&modificationDate=14738847656731474056136413&api=v2" class="feature-icon"></a> <div class="feature-description"> <h2 data-toggle="tooltip" title="Process, Criteria, Templates and Reports">Standards Selection</h2> <p>A Process and a Space for building and using Standards Selection Guides </p> <p><span style="font-weight:bold;color:#e02e3b;">Standards</span> are an integral piece of the interoperability solution, covering both the terminology that defines the data sent, and the messaging structures that define how the data is transferred. The framework provides the access and consideration criteria to the international and Canadian standards to facilitate implementation.</p> <ul class="guides-list" style="display:none;"> <li><a href="">Latest Standards Release</a></li> <li><a href="/display/SSG/Process">Process<">Terminology Subsets</a></li> <li><a href="/display/SSG/Appendix+A+-+Standards+Assessment+-+template">Assessment template</a></li> <li><a href="/display/SSG/Appendix+B+-+Selection+Guide+-+template">Guide template<">Previous versions of pan Canadian Messaging Standards</a></li> <li><a href="/display/GR">Guide Registry</a></li> </ul> </div> </div> <div class="col-md-15 feature-box"> <a href="/display/SR" class="centered" data-toggle="tooltip" title="Specifications"> <img src="/download/attachments/3048882/specifications.png?version=1&modificationDate=1473884765279&api=v2" class="feature-icon"> </a> <div class="feature-description"> <h2 data-toggle="tooltip" title="Specifications">Specifications</h2> <p>Information interoperability and technicnal interoperability <p><span style="font-weight:bold;color:#e02e3b;">Specifications</span> provide the details for the solution to be implemented. These details include: a review of the data elements used, samples of transferred messages, the system architecture as well as the security specifications including authorization and authentication.</p> <ul class="guides-list" style="display:none;"> <li><a href="https://infoscribe.infoway-inforoute.ca/display/EPSPEC/Home+Page">Business Requirements</a></li> </ul> </div> </div> </div> </div> |
Page History
Overview
Content Tools