StructureMap FHIR Resource Proposal
This page documents a Approved FHIR Resource Proposal
Contents
- 1 StructureMap
- 1.1 Owning committee name
- 1.2 Committee Approval Date:
- 1.3 Contributing or Reviewing Work Groups
- 1.4 FHIR Resource Development Project Insight ID
- 1.5 Scope of coverage
- 1.6 RIM scope
- 1.7 Resource appropriateness
- 1.8 Expected implementations
- 1.9 Content sources
- 1.10 Example Scenarios
- 1.11 Resource Relationships
- 1.12 Timelines
- 1.13 gForge Users
- 1.14 When Resource Proposal Is Complete
StructureMap
Owning committee name
FHIR_Infrastructure
Committee Approval Date:
FHIR-I: 2016-03-07
Contributing or Reviewing Work Groups
- ITS
- SD
- MnM
FHIR Resource Development Project Insight ID
1207
Scope of coverage
This resource will define an executable mapping from one structure to another, that can be executed by an processor that will convert instances of data from the source structure definition to the target structure definition. The scope of this resource is conversion from any structure that can be defined using a structure definition resource to any other structure. This includes resources and data types, and also logical models.
As an infrastructure resource, subject/discipline/delivery/locale are all not related. The scope of the resource is the challenges encountered when specifying and executing a transformation between two instances of data with different structures.
RIM scope
Out of scope for the RIM
Resource appropriateness
- Mapping is a well understood concept that occurs ubiquitously throughout the implementation space
- Maps are maintained in an ongoing fashion, and can be shared/searched etc
- Mapping BOF at Orlando meeting established a clear desire for a trading eco-system around executable maps
- expected to contain around 20-25 elements
Expected implementations
- Ken Lord's MDMI tool
- FHIR Build tool
- Trifolia
Others will be expected
Content sources
OMG mapping specifications:
- MDMI
- QVT
- requirements from the Mapping BOF
- requirements as discovered in (C)CDA/FHIR Mapping projects (incl Argonaut)
Example Scenarios
Resource Relationships
The StructureMap resource Will depend on having structure definitions, but it's possible to use it without them, if there's no reference to types. The StructureMap resource will depend on the engine having access to a terminology server, and will make implicit references to value sets and concept maps The StructureMap resource differs from the ConceptMap resource in the ConceptMap resource describes mappings between concepts without considering the details of instance management, value domain space and external content dependencies
Timelines
Draft for Montreal connectathon, then part of DSTU3
gForge Users
Grahame
When Resource Proposal Is Complete
When you have completed your proposal, please send an email to FMGcontact@HL7.org
