openPASSOpen Privacy, Access and Security Services
Project Status ReportApril 9, 2009
openPASS Boca Chart2Q2009
-HL7 SOA PASS Service Functional and Platform Independent Models
-Successful recruitment
-Consensus Reference Architecture
-Jurisdictional standards
-Jurisdictional laws and regulations
-Healthcare document/message standards
Dependencies
Packaging Editions
-Recruit project/subproject leadership
-Initial implementation priorities --Audit (basic) --Secure transport --Security context --Policy-driven access control (basic)
-Prioritized Use Cases
-Service inventory prioritization
-Alignment with Reference Architecture
-Review/adapt OHF code base -IHE ATNA
-Work out service orchestration strategy
-Identity Resolution (in support of basic user/patient context coordination)
Content-Resource constraints
-Delays in emerging standards
-Several services required to be useful
-Composition required to be useful
-Requires domain expert engagement
-Divergence of related standards efforts
-Jurisdictional standards differences
-Jurisdictional regulatory differences
Pressures/Exposures Added
Deleted & Changed
Q2 09 - Audit subproject plan published
- Access control subproject plan published
Milestones
openPASS Roadmap
3Q 2009
Guiding Principles:
•Align with HL7-SOA PASS Service Functional Models
•Build service inventory of composable components
•Support OHT Reference Architecture requirements
Developerrecruiting
2Q2009
4Q 20091st Milestone
Release
PASS-AuditInitial component releases
PASS-Identity, AccessInitial component releases
April 2009
June 2009
Subproject Plans Published
Development begins
1Q 2010