This wiki has undergone a migration to Confluence found Here

201605 Declarative Mapping

From HL7Wiki
Revision as of 23:17, 9 February 2016 by Ioana13 (talk | contribs) (Declarative Mapping Connectathon Track)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Return to May 2016 Proposals

Declarative Mapping

This track will explore mappings and/or a useful subset of mapping tasks using declarative languages used to address interoperability issues.

  • Pre-requisites: none

Submitting WG/Project/Implementer Group

  • SOA Working Group
  • CGIT (approval planned)
  • CCBC (approvalplanned)

Justification

There is a recognized need for mappings to facilitate interoperability across HL7 products Following on the Birds of a Feather CDA to FHIR session in Orlando, there was an agreement among the participants to pursue declarative approaches or mappings. Objectives of the track include reuseable computable artifacts that can be saved / persisted as FHIR resources from the approaches presented in the Connectathon. SOA WG has already developed "cross-paradigm" mapping guidance intended to represent the same business content in more than on structure (e.g. CDA template to FHIR profile or V2 profile components)


Proposed Track Lead

Expected participants

The expected participants include:

  • Keith Dudley / Grahame Grieve
  • MDMI Open Source Project (several participants)
  • David Booth (Yosemite Project)
  • SAMHSA BHITS Project
  • Members of the i2b2 on FHIR team

Roles

FHIR Client

FHIR Client will....

FHIR Server

FHIR Server will....

Scenarios

Desclarative Mapping Use Cases:

[To do: create scenarios based on the planned scops for May and expected resources]

1. Create a new map

Precondition: ...

Action:

...

Success Criteria:

...

2. Publish a map

Precondition:

Action:

An event is published to designated topic

Success Criteria:

Bonus Point:

3. Execute a map

Precondition:

Action:


Success Criteria:


Bonus Point: