Difference between revisions of "Frameworks"

From IHE Wiki
Jump to: navigation, search
m
(Undo revision 48448 by AveMaria (Talk))
Line 5: Line 5:
  
 
Technical frameworks are published in '''volumes'''. The first volume typically defines the Profile, the use cases, the '''[[Actors|actors]]''' involved and the requirements for conformance. Subsequent volume(s) specify how to implement the transactions used in the Profiles. The last volume is usually reserved for National / Regional extensions.
 
Technical frameworks are published in '''volumes'''. The first volume typically defines the Profile, the use cases, the '''[[Actors|actors]]''' involved and the requirements for conformance. Subsequent volume(s) specify how to implement the transactions used in the Profiles. The last volume is usually reserved for National / Regional extensions.
 
===Objective & scope===
 
The aim is to extend the IHE initiative to [http://riftgold.wordpress.com/2011/02/21/is-rift-better-than-wow/ wow gold] anatomic pathology laboratories, their [http://dcuocash.wordpress.com/2011/02/22/dcuo-reviews/ dcuo cash] information, automation, imaging systems and equipments.
 
 
 
The scope of the [http://riftgold.wordpress.com/2011/02/22/rift-class-guide/ rift plat] anatomic pathology includes [http://www.gamerking.com/rift-character-creation-guide/ rift plat] surgical pathology, [http://www.warcraftgold.com/rift-toon-creation-guide/ rift plat] biopsies pathology, [http://www.ffxifactory.com/rift-character-creation-walkthrough/ rift plat] cytopathology, [http://www.platsupply.com/rift-toon-creation-walkthrough/ rift plat] autopsies, and other [http://atanium.blogspot.com/2011/02/rift-guide-how-to-create-new-character.html rift plat] related techniques (immunohistochemistry, molecular pathology, etc).
 
 
 
Information systems in anatomic [http://riftgold.wordpress.com/2011/02/23/rift-guide-how-to-build-a-fresh-toon/ rift plat] pathology laboratories gather medical data (text, images, etc) throughout the [http://riftgold.wordpress.com/2011/02/24/rifts-official-server-list/ rift plat] specimen management from specimen reception to report editing.
 
 
 
The diagnostic process in [http://yourgameupdates.blogspot.com/2011/02/dcuo-first-patch-goes-live.html dcuo cash] anatomical pathology (figure 1) differs from that in the clinical laboratory since it relies on image interpretation and [http://yourgameupdates.blogspot.com/2011/01/left-4-dead-2-cheats.html left 4 dead 2 cheats]. It also differs from that in radiology since it is specimen-driven and when digital imaging is performed many types of imaging equipments (gross imaging, microscopic still imaging, whole slide imaging, multispectral imaging, etc) may be involved for a single examination. Moreover, with [http://manuelcadaing.com/godaddy-promo-code-and-coupon-list/ GoDaddy Promo Code] you'll be advance in game and images of the same study may be related to different specimen (parts and/or slides) from one or even different patients (e.g Tissue Micro Array). Finally with [http://manuelcadaing.com/seo-elite-review/ SEO Elite Review], slides are always available to acquire more images, if needed. In radiology, the diagnostic process is patient-driven, an examination (study) usually involves a single image acquisition modality and all images of the study are related to one and only one patient.
 
  
  

Revision as of 09:22, 24 February 2011

IHE Technical Frameworks

IHE Technical Frameworks specify the technical details of the Integration Profiles. Each IHE Domain publishes Technical Framework which are used by engineers to implement IHE functionality.

Technical frameworks are published in volumes. The first volume typically defines the Profile, the use cases, the actors involved and the requirements for conformance. Subsequent volume(s) specify how to implement the transactions used in the Profiles. The last volume is usually reserved for National / Regional extensions.


Official Publication

www.ihe.net/Technical_Framework


Public Comment Drafts

www.ihe.net/Technical_Framework/public_comment.cfm


Maintenance

Change Proposals are fixes and clarifications which get incorporated into a Technical Framework.


See Also

Technical Framework Development Process for details on how they are organized and how they are developed.