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

Difference between revisions of "EA Alpha PASS"

From HL7Wiki
Jump to navigation Jump to search
 
(One intermediate revision by the same user not shown)
Line 252: Line 252:
 
|This type of tooling will be done if implementers are interested in it.
 
|This type of tooling will be done if implementers are interested in it.
 
|}
 
|}
 +
 +
===Status of PASS balloting===
 +
2009-12-11: PASS Access Control will ballot; Architecture Framework not proceeding to ballot Jan2010.  Access Control scped across three of the four RM-ODP viewpoints, business, informational and computational.  Planning to go DSTU.
 +
 +
 +
====Access Control====
 +
*HL7 Version 3 Standard: Privacy, Access and Security Services (PASS) - Access Control, PIM Level, Release 1 [HL7 PASS AC PIM R1 ]
 +
* HL7 Version 3 Standard: Privacy, Access and Security Services (PASS) - Access Control, PIM Level, Release 1 - DSTU May 2010 postponed
 +
*HL7 Version 3 Standard: Privacy, Access and Security Services - Access Control, Release 1 - '''DSTU 2010Jan'''
 +
 +
====Audit====
 +
*HL7 Version 3 Standard: Privacy, Access and Security Services (PASS) - Audit, Conceptual Level, Release 1 [HL7 PASS AUDIT CL R1 ] - DSTU May 2010 postponed
 +
* HL7 Version 3 Standard: Privacy, Access and Security Services (PASS) - Audit Services, Release 1 - '''DSTU September 2010 '''
 +
 +
====Architecture Framework====
 +
*HL7 Version 3 Standard: Privacy, Access and Security Services (PASS) Architecture Framework, Release 1 [HL7 PASS AF R1 ] - Informative 2010Jan postponed
 +
 +
====Functional Model====
 +
*HL7 Version 3 Standard: Privacy, Access and Security Services (PASS) Functional Model, Release 1 [HL7 PASS FM R1 2007] - no status

Latest revision as of 19:10, 28 September 2010

Alpha Project - PASS

Baseline Artifact Assessment - Architecture Framework

Spec. Topic / Viewpoint Candidate Alpha Project’s Current or Planned Artifacts Current State (Existence, Completeness, Known Issues, etc.) Planned Approach
Blueprint Enterprise / Business Viewpoint Domain Business Context
  • Glossary
  • Use Cases
  • Requirements
In process. Build on subproject work from the last 2 years.
Information viewpoint Domain Analysis Model
Domain Information Model
In process. Developed concurrently.
Computational viewpoint Collaboration Analysis In process. Aligned with related subproject specs to ensure proper tie-in.
Engineering viewpoint . . .
Platform –Independent Enterprise / Business Viewpoint . . .
Information viewpoint
  • Domain Messaging Models
  • Message Definition
  • Vocabularies
. Build on conceptual models.
Computational viewpoint Service Behavioral Model . Build on conceptual models.
Engineering viewpoint . . .
Platform-Specific Enterprise / Business Viewpoint . . .
Information viewpoint Message Schema Binding . Build on conceptual and PIM models. Target alignment with key existing implementations
Computational viewpoint Collaboration scripts . Build on conceptual and PIM models. Target alignment with key existing implementations
Engineering viewpoint . . .


Baseline Artifact Assessment - Audit, Access Control, Identity and Consent

Spec. Topic / Viewpoint Candidate Alpha Project’s Current or Planned Artifacts Current State (Existence, Completeness, Known Issues, etc.) Planned Approach
Blueprint Enterprise / Business Viewpoint Domain Analysis Model In process. Core working team creates all documentation and is:
  1. Assessed by the Review Team for feedback.
  2. Reviewed by project leads to ensure tie into PASS AF
Information viewpoint Domain Information Model In process. Developed concurrently with Domain Analysis Models.
Computational viewpoint

Functional Model
Collaboration Analysis
Conformance Statements

Access, Audit and Consent in process. Builds on Domain Analysis and Domain Information Models
Engineering viewpoint . . .
Platform –Independent Enterprise / Business Viewpoint . . .
Information viewpoint
  • Domain Information Models
  • Conext Information Model
  • Semantic Profiles
. Build on conceptual models.
Computational viewpoint

Service Behavioral Model
Functional Profiles

. Build on conceptual models.
Engineering viewpoint . . .
Platform-Specific Enterprise / Business Viewpoint . . PSM level documents can be created independently but will use above review process for documentation.
Information viewpoint Context Token XML Schema . Build on conceptual and PIM models. Target alignment with key existing implementations
Computational viewpoint

Platform Binding - Web services
Profiles

. Build on conceptual and PIM models. Target alignment with key existing implementations
Engineering viewpoint . . .


Baseline Artifact Assessment - Privacy Consent Directive DAM

Spec. Topic / Viewpoint Candidate Alpha Project’s Current or Planned Artifacts Current State (Existence, Completeness, Known Issues, etc.) Planned Approach
Blueprint Enterprise / Business Viewpoint

Business Use Case Analysis (DAM, Sections 1.1, 1.2)

Balloted as informative in Jan.2009 .
Information viewpoint

Information and Terminology Analysis in DAM Chapters 2, 3, 4, 5

Balloted as informative in Jan.2009 .
Computational viewpoint

Interactions/collaborations analysis in DAM Section 1.3

Balloted as informative in Jan.2009 .
Engineering viewpoint . . .
Platform –Independent Enterprise / Business Viewpoint

CPC D Section 1

Balloted as draft for comment May 2009 To be balloted as DSTU in Sept. 2009
Information viewpoint

CPC D Section 2

Balloted as draft for comment May 2009 To be balloted as DSTU in Sept. 2009
Computational viewpoint

CPC D Section 3

Balloted as draft for comment May 2009 To be balloted as DSTU in Sept. 2009
Engineering viewpoint Mapping algorithm to XACML, ODRL In progress To be published with the ballot
Platform-Specific Enterprise / Business Viewpoint . . .
Information viewpoint XSD Available To be published with the ballot
Computational viewpoint WSDL Available To be published with the ballot
Engineering viewpoint Pilot implementation for mapping to XACML, ODRL Planned This type of tooling will be done if implementers are interested in it.

Status of PASS balloting

2009-12-11: PASS Access Control will ballot; Architecture Framework not proceeding to ballot Jan2010. Access Control scped across three of the four RM-ODP viewpoints, business, informational and computational. Planning to go DSTU.


Access Control

  • HL7 Version 3 Standard: Privacy, Access and Security Services (PASS) - Access Control, PIM Level, Release 1 [HL7 PASS AC PIM R1 ]
  • HL7 Version 3 Standard: Privacy, Access and Security Services (PASS) - Access Control, PIM Level, Release 1 - DSTU May 2010 postponed
  • HL7 Version 3 Standard: Privacy, Access and Security Services - Access Control, Release 1 - DSTU 2010Jan

Audit

  • HL7 Version 3 Standard: Privacy, Access and Security Services (PASS) - Audit, Conceptual Level, Release 1 [HL7 PASS AUDIT CL R1 ] - DSTU May 2010 postponed
  • HL7 Version 3 Standard: Privacy, Access and Security Services (PASS) - Audit Services, Release 1 - DSTU September 2010

Architecture Framework

  • HL7 Version 3 Standard: Privacy, Access and Security Services (PASS) Architecture Framework, Release 1 [HL7 PASS AF R1 ] - Informative 2010Jan postponed

Functional Model

  • HL7 Version 3 Standard: Privacy, Access and Security Services (PASS) Functional Model, Release 1 [HL7 PASS FM R1 2007] - no status