This wiki has undergone a migration to Confluence found Here

Difference between revisions of "FHIR Connectathon 1"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "A FHIR Connectathon will be held on Saturday September 8th, 2012. The connectathon is sponsored by the [[RIMBAA] WG, all FHIR implementers are welcome to join in the event. Scen...")
 
Line 1: Line 1:
A FHIR Connectathon will be held on Saturday September 8th, 2012. The connectathon is sponsored by the [[RIMBAA] WG, all FHIR implementers are welcome to join in the event.
+
= Event Planning =
 +
 
 +
A FHIR Connectathon will be held on Baltimore USA on Saturday September 8th, 2012.  
 +
The connectathon is sponsored by the [[RIMBAA] WG, all FHIR implementers are welcome to join in the event.
 +
 
 +
= Scenario =
  
 
Scenario: actors and workflows related to two resources: [http://www.hl7.org/implement/standards/fhir/person.htm persons], and [http://www.hl7.org/implement/standards/fhir/constraint.htm constraint profiles]
 
Scenario: actors and workflows related to two resources: [http://www.hl7.org/implement/standards/fhir/person.htm persons], and [http://www.hl7.org/implement/standards/fhir/constraint.htm constraint profiles]
 +
 +
== Profiles ==
 +
 +
Actors:
 +
* Profile Author
 +
** allows users to create profiles
 +
* Profile Server
 +
** provides a RESTful service (per FHIR spec) for Profiles
 +
* Profile User
 +
** provides user access to profiles on Profile Server (find/retrieve/change etc)
 +
 +
Scenario:
 +
* system analyst A defines a profile on a Person resource
 +
* submits it to a Profile registry
 +
* Implementer B searches for Profile, and accesses it
 +
 +
== Person ==
 +
 +
Actors
 +
* ?
 +
 +
Scenario
 +
* ?

Revision as of 20:22, 23 May 2012

Event Planning

A FHIR Connectathon will be held on Baltimore USA on Saturday September 8th, 2012. The connectathon is sponsored by the [[RIMBAA] WG, all FHIR implementers are welcome to join in the event.

Scenario

Scenario: actors and workflows related to two resources: persons, and constraint profiles

Profiles

Actors:

  • Profile Author
** allows users to create profiles
  • Profile Server
** provides a RESTful service (per FHIR spec) for Profiles
  • Profile User
** provides user access to profiles on Profile Server (find/retrieve/change etc)

Scenario:

  • system analyst A defines a profile on a Person resource
  • submits it to a Profile registry
  • Implementer B searches for Profile, and accesses it

Person

Actors

  •  ?

Scenario

  •  ?