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

Difference between revisions of "ConceptMap FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "{{subst::Template:FHIR Resource Proposal}}")
 
Line 1: Line 1:
−
 
 
<div class="messagebox cleanup metadata">
 
<div class="messagebox cleanup metadata">
 
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
Line 13: Line 12:
  
  
−
=PutProposedResourceNameHere=
+
=ConceptMap=
−
 
 
−
<!-- Resource names should meet the following characteristics:
 
−
* 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==
 
==Owning committee name==
  
−
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. -->
+
[[FHIR]] Project Team
−
[[YourCommitteeName]]
 
  
 
==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) -->
+
* Vocabulary
−
* Work Group Name
 
−
* or link
 
−
* 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 -->
+
Whichever one FHIR works under
  
 
==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 expresses a mapping from one value set to another.  
−
 
+
Each mapping has the following qualities:
−
Scope should consider numerous aspects of breadth of scope, including:
+
* a unidirectional mapping
−
* Subject: Human vs. non-human vs. non-patient (e.g. lab bench medicine)
+
* from a concept in one system to a concept in another
−
* Disciplines: Environmental Health, Palliative, Respiratory, Psychology, Maternity, Clinical Research
+
* the mapping is only claimed to be valid in the context of the source and target value set.
−
* Delivery environment (Community, Geriatric, Home care, Emergency, Inpatient, Intensive, Neonatal, Pediatric, Primary)
+
* supports mapping between any code system as defined by the value set resource (and by extension, the core principles)
−
* Locale: Country, region
+
* This will be used to capture and share mappings between code systems
−
 
+
* scope is not constrained by subject, discipline, environment, or locale
−
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 - this is in the MIF space.
  
 
==Resource appropriateness==
 
==Resource appropriateness==
  
−
<!-- Does the resource meet the following characteristics?
+
This resource:
−
 
+
* Represents a well understood, "important" concept in the business of healthcare: mapping between code systems
−
Must
+
* Represents a concept expected to be tracked with distinct, reliable, unique ids: maps a important and expensive assets to be tracked and shared
−
* Represents a well understood, "important" concept in the business of healthcare
+
* Reasonable for the resource to be independently created, queried and maintained: yes - maps get created and curated
−
* Represents a concept expected to be tracked with distinct, reliable, unique ids
+
* Declared interest in need for standardization of data exchange: yes - there is need both exchange maps and also to use maps in service of exchange
−
* Reasonable for the resource to be independently created, queried and maintained
+
* Resource is expected to contain an appropriate number of "core" (non-extension): current design has 19 elements
−
 
+
* Have the characteristics of high cohesion & low coupling: this is a focused infrastructure resource with a clearly defind boundary
−
Should
 
−
* 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==
 
==Expected implementations==
  
−
<!--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. -->
+
* this is already implemented by the tools to express FHIR mappings to v2 and v3, and will be used by the run-time tool to assist with validation and operational mappings
 +
* this will be used underneath implementations of the questionnaire resource to capture mappings of data elements and their contents between systems
 +
* this would be taken up by any FHIR based implementation of vocabulary related services
 +
* profile editors will need to express code mappings on a regular basis
  
 
==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
+
* Internal tooling requirements
 +
* MIF
 +
* CTS 2
 +
* Core Principles
 +
* IHTSDO Mapping format
  
−
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? -->
 
  
 
==Example Scenarios==
 
==Example Scenarios==
  
−
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource.  They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) -->
+
* mappings from FHIR to v2 and v3
 +
* mappings from a local code set to a LOINC code set
  
 
==Resource Relationships==
 
==Resource Relationships==
  
−
<!-- What are the resources do you expect will reference this resource and in what context?
+
* this resource references ValueSet.
−
 
+
* No direct plans for other resources to reference it yet, but it may impact in future planning for the Profile resource
−
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 -->
+
* This resource already exists in an operational non-reviewed form
 +
* in it's existing form, it wasn't proposed for the DSTU, and therefore would be post DSTU
 +
* However the tools need it to exist to meet DSTU comments around code mappings needing to be provided
 +
* proposal is to publish as informative with the DSTU (with disclaimer explaining the status), and address comments in a future DSTU
  
 
==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

Revision as of 22:54, 3 October 2013

OpenHotTopic.GIF

This page documents a Pending FHIR Resource Proposal



ConceptMap

Owning committee name

FHIR Project Team

Contributing or Reviewing Work Groups

  • Vocabulary

FHIR Resource Development Project Insight ID

Whichever one FHIR works under

Scope of coverage

This resource expresses a mapping from one value set to another. Each mapping has the following qualities:

  • a unidirectional mapping
  • from a concept in one system to a concept in another
  • the mapping is only claimed to be valid in the context of the source and target value set.
  • supports mapping between any code system as defined by the value set resource (and by extension, the core principles)
  • This will be used to capture and share mappings between code systems
  • scope is not constrained by subject, discipline, environment, or locale

RIM scope

Out of scope for the RIM - this is in the MIF space.

Resource appropriateness

This resource:

  • Represents a well understood, "important" concept in the business of healthcare: mapping between code systems
  • Represents a concept expected to be tracked with distinct, reliable, unique ids: maps a important and expensive assets to be tracked and shared
  • Reasonable for the resource to be independently created, queried and maintained: yes - maps get created and curated
  • Declared interest in need for standardization of data exchange: yes - there is need both exchange maps and also to use maps in service of exchange
  • Resource is expected to contain an appropriate number of "core" (non-extension): current design has 19 elements
  • Have the characteristics of high cohesion & low coupling: this is a focused infrastructure resource with a clearly defind boundary
-->

Expected implementations

  • this is already implemented by the tools to express FHIR mappings to v2 and v3, and will be used by the run-time tool to assist with validation and operational mappings
  • this will be used underneath implementations of the questionnaire resource to capture mappings of data elements and their contents between systems
  • this would be taken up by any FHIR based implementation of vocabulary related services
  • profile editors will need to express code mappings on a regular basis

Content sources

  • Internal tooling requirements
  • MIF
  • CTS 2
  • Core Principles
  • IHTSDO Mapping format


Example Scenarios

  • mappings from FHIR to v2 and v3
  • mappings from a local code set to a LOINC code set

Resource Relationships

  • this resource references ValueSet.
  • No direct plans for other resources to reference it yet, but it may impact in future planning for the Profile resource

Timelines

  • This resource already exists in an operational non-reviewed form
  • in it's existing form, it wasn't proposed for the DSTU, and therefore would be post DSTU
  • However the tools need it to exist to meet DSTU comments around code mappings needing to be provided
  • proposal is to publish as informative with the DSTU (with disclaimer explaining the status), and address comments in a future DSTU

gForge Users

Grahame

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