Difference between revisions of "201801 Profiling"
Mark Kramer (talk | contribs) |
Mark Kramer (talk | contribs) |
||
| Line 52: | Line 52: | ||
I am happy to help: JohnMoehrke@gmail.com -- security co-chair | I am happy to help: JohnMoehrke@gmail.com -- security co-chair | ||
--> | --> | ||
| + | none | ||
Revision as of 01:24, 19 October 2017
Track Name
Domain Analysis Model to FHIR Profiles and Implementation Guide
Submitting WG/Project/Implementer Group
Clinical Interoperability Council, Cancer Interoperability Group
Justification
There is a practical gap between documenting the clinical content in a healthcare domain via a domain analysis model, and the ability to deliver a corresponding FHIR implementation. While it is possible with existing manual tools to create FHIR Profiles in small numbers, when a domain requires 20, 50, or 100 profiles, efficient specification and automation is required. This track will to test a proposed methodology for creating FHIR profiles that should make it possible to convert a domain analysis model to a set of FHIR profiles in a relatively simple, efficient manner.
Proposed Track Lead
Mark Kramer, mkramer@mitre.org
Michael O'Keefe, mokeefe@mitre.org
See Connectathon_Track_Lead_Responsibilities
Expected participants
TBD
Roles
Please include information here regarding how much advance preparation will be required if creating a client and/or server.
Role 1 Name
Scenarios
Scenario Step 1 Name
- Action:
- Precondition:
- Success Criteria:
- Bonus point:
TestScript(s)
Security and Privacy Considerations
none
