This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "EA IP"

From HL7Wiki
Jump to navigation Jump to search
Line 33: Line 33:
 
**#ACS Cardiology DAM
 
**#ACS Cardiology DAM
 
**#Great Ormond Street Hospital for Children, London, UK (David Bowen)
 
**#Great Ormond Street Hospital for Children, London, UK (David Bowen)
 +
*John Koisch in an [http://newgforge.hl7.nscee.edu/docman/view.php/52/886/JKoisch_email_20090126.pdf email] from the ArB for consideration by the TSC proposed, listed by project, with some brief notes about why the ArB thinks they are interesting <<as>> Alpha projects:
 +
*#DOD VA EHR-FM -- Message portfolio ; Creates analysis specs for prioritized EHR profiles
 +
*#Pa Registies (More than one) -- Most of the analysis done, service interfaces
 +
*#COPPA - National Person Registry; Captures RIM semantics, uses instances of the Behavioral Framework(BF); Set of artifacts already done
 +
*#OO -- Complex Behavioral models(instances of the Behavioral Framework(BF)) and access patterns
 +
*#Patient access to quality care (PAQC)  -- Infoway; Messaging expressed in a services metaphor
 +
*#CTS2 -- Terminology Services
 +
*#Medicine Identity Reconcillation -- PHARMA ; Pushes on OMG harmonization ; Uses EIS for medicine identification
 +
*#PASS -- Directing OHT to pull together the work from MCI, Infoway, NeHTA, NHS
 +
*#PHER -- Immunization registry.

Revision as of 19:56, 26 January 2009

Enterprise Architecture Implementation Project (EA IP)

This Wiki page was created for the HL7 Enterprise Architecture Implementation Project (EA IP). The Architecture Board is a TSC-appointed committee to define an architecture for the work of the HL7 body. The TSC is responsible for the rollout of that architecture. This site is intended to both provide and elicit communication on, for and about the Implementation Project.

General Information

Presentation Materials

Discussion Items

Comments

Please use the discussion tab above.

Implementation Plans

  • Discussion has occurred various implementation approaches, including
    • Top-down reorganization
    • Bottom-up test, or "alpha" projects
  • where the "alpha" project would be a sub-project of the architecture rollout.
    • Alpha project candidates or volunteers include:
      1. NCI deployed four services last Monday (20090105)developed under SAEAF architecture.
      2. US VA/DOD project is poised as alpha project [1] TSC Tracker #858
      3. ACS Cardiology DAM
      4. Great Ormond Street Hospital for Children, London, UK (David Bowen)
  • John Koisch in an email from the ArB for consideration by the TSC proposed, listed by project, with some brief notes about why the ArB thinks they are interesting <<as>> Alpha projects:
    1. DOD VA EHR-FM -- Message portfolio ; Creates analysis specs for prioritized EHR profiles
    2. Pa Registies (More than one) -- Most of the analysis done, service interfaces
    3. COPPA - National Person Registry; Captures RIM semantics, uses instances of the Behavioral Framework(BF); Set of artifacts already done
    4. OO -- Complex Behavioral models(instances of the Behavioral Framework(BF)) and access patterns
    5. Patient access to quality care (PAQC) -- Infoway; Messaging expressed in a services metaphor
    6. CTS2 -- Terminology Services
    7. Medicine Identity Reconcillation -- PHARMA ; Pushes on OMG harmonization ; Uses EIS for medicine identification
    8. PASS -- Directing OHT to pull together the work from MCI, Infoway, NeHTA, NHS
    9. PHER -- Immunization registry.