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

Difference between revisions of "StructureMap FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
Line 13: Line 13:
  
  
−
=PutProposedResourceNameHere=
+
=StructureMap=
  
−
<!-- Resource names should meet the following characteristics:
+
==Owning committee name==
−
* Lower camel case
 
−
* U.S. English
 
−
* Domain-friendly
 
−
* Short
 
−
* Clear
 
−
* Unique
 
−
* Avoid non-universal abbreviations (e.g. URL would be ok)
 
−
* Be expressed as a noun
 
−
* Be consistent with other similar resources
 
−
-->
 
  
−
==Owning committee name==
+
FHIR_Infrastructure
  
−
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. -->
 
−
[[YourCommitteeName]]
 
 
==Committee Approval Date:==
 
==Committee Approval Date:==
−
<i>Please enter the date that the committee approved this Resource proposal</i>
+
 
 +
<i>Yet to be approved</i>
  
 
==Contributing or Reviewing Work Groups==
 
==Contributing or Reviewing Work Groups==
  
−
<!-- Additional work groups that may have an interest in contributing to, or reviewing  the content of the resource (optional) -->
+
* ITS
−
* Work Group Name
+
* SD
−
* or link
+
* MnM
−
* or "None"
 
  
 
==FHIR Resource Development Project Insight ID==
 
==FHIR Resource Development Project Insight ID==
  
−
<!-- Please specify the id of your work group’s PSS for doing FHIR work.  (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc -->
+
1207
  
 
==Scope of coverage==
 
==Scope of coverage==
  
−
<!-- Define the full scope of coverage for the resource. The scope must be clearly delineated such that it does not overlap with any other existing or expected resource.  The scope will be used to govern "what is the set of potential applications to consider when evaluating what elements are 'core' – i.e. in the 80%"
+
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.  
  
−
Scope should consider numerous aspects of breadth of scope, including:
+
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.  
−
* Subject: Human vs. non-human vs. non-patient (e.g. lab bench medicine)
 
−
* Disciplines: Environmental Health, Palliative, Respiratory, Psychology, Maternity, Clinical Research
 
−
* Delivery environment (Community, Geriatric, Home care, Emergency, Inpatient, Intensive, Neonatal, Pediatric, Primary)
 
−
* Locale: Country, region
 
−
 
 
−
As a rule, resources should encompass all of these aspects.
 
−
-->
 
  
 
==RIM scope==
 
==RIM scope==
  
−
<!-- Identify the formal RIM mapping for the root concept of the resource.  The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. -->
+
Out of scope for the RIM
  
 
==Resource appropriateness==
 
==Resource appropriateness==
  
−
<!-- Does the resource meet the following characteristics?
+
* 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
  
−
Must
 
−
* Represents a well understood, "important" concept in the business of healthcare
 
−
* Represents a concept expected to be tracked with distinct, reliable, unique ids
 
−
* Reasonable for the resource to be independently created, queried and maintained
 
  
−
Should
+
==Expected implementations==
−
* Declared interest in need for standardization of data exchange</span>
 
−
* Resource is expected to contain an appropriate number of "core" (non-extension) data elements (in most cases, somewhere in the range of 20-50)
 
−
* Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document
 
−
-->
 
  
−
==Expected implementations==
+
* Ken Lord's MDMI tool
 +
* FHIR Build tool
 +
* Trifolia
  
−
<!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. -->
+
Others will be expected
  
 
==Content sources==
 
==Content sources==
  
−
<!-- List all of the specifications (beyond those in the "standard" (FHIR_Design_Requirements_Sources) list of source specifications) that you’re planning to consult
+
OMG mapping specifications:
 +
* MDMI
 +
* QVT
 +
* requirements from the Mapping BOF
 +
* requirements as discovered in (C)CDA/FHIR Mapping projects (incl Argonaut)
  
−
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? -->
 
  
 
==Example Scenarios==
 
==Example Scenarios==
Line 93: Line 75:
 
==Resource Relationships==
 
==Resource Relationships==
  
−
<!-- What are the resources do you expect will reference this resource and in what context?
+
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
−
What resources do you expect this resource reference and in what context?
+
   
−
 
 
−
Note: These may be existing resources or "expected" resource
 
−
 
 
−
Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording)
 
−
  -->
 
−
 
 
 
==Timelines==
 
==Timelines==
  
−
<!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting -->
+
Draft for Montreal connectathon, then part of DSTU3
  
 
==gForge Users==
 
==gForge Users==
  
−
<!-- Identify the userids who will require commit access to gForge to maintain the resource.  (Ensure all users have registered for gForge.) -->
+
Grahame
  
 
==When Resource Proposal Is Complete==
 
==When Resource Proposal Is Complete==
 
'''When you have completed your proposal, please send an email to [mailto:FMGcontact@HL7.org FMGcontact@HL7.org]'''
 
'''When you have completed your proposal, please send an email to [mailto:FMGcontact@HL7.org FMGcontact@HL7.org]'''

Revision as of 22:09, 18 February 2016

OpenHotTopic.GIF

This page documents a Pending FHIR Resource Proposal



StructureMap

Owning committee name

FHIR_Infrastructure

Committee Approval Date:

Yet to be approved

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

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

Retrieved from "https://wiki.hl7.org/w/index.php?title=StructureMap_FHIR_Resource_Proposal&oldid=115516"