Difference between revisions of "Breast Radiology FHIR IG Proposal"

From HL7Wiki
Jump to navigation Jump to search
m (Llaakso moved page FHIR Profile Proposal to Breast Radiology FHIR IG Proposal: for R Esmond)
 
Line 78: Line 78:
 
     Informative Jan 2020 Ballot
 
     Informative Jan 2020 Ballot
 
     STU May 2020 Ballot
 
     STU May 2020 Ballot
 +
 +
 +
<div class="messagebox cleanup metadata">
 +
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 +
<div style="background:#F0F0F0">
 +
This page documents a [[:category:Pending FHIR IG Proposal|Pending]] [[:category:FHIR IG Proposal|FHIR IG Proposal]]
 +
</div>
 +
</div>
 +
[[Category:FHIR IG Proposal]]
 +
[[Category:Pending FHIR IG Proposal]]
 +
 +
 +
<!-- For additional guidance on considerations for resource creation, refer to [[FHIR IG Considerations]] -->
 +
 +
 +
=PutProposedIGNameHere=
 +
 +
<!-- Resource names should meet the following characteristics:
 +
* Title Case
 +
* U.S. English
 +
* Domain-friendly
 +
* Short
 +
* Clear
 +
* Unique
 +
* Avoid non-universal abbreviations (e.g. URL would be ok)
 +
* Be consistent with other similar IGs
 +
-->
 +
 +
==Owning work group name==
 +
 +
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the IG. -->
 +
[[YourWorkGroupName]]
 +
 +
==Committee Approval Date:==
 +
<i>Please enter the date that the committee approved this IGproposal</i>
 +
 +
==Publishing Lead==
 +
 +
<!--Name and email of the primary contact for the FMG with respect to publishing for this IG?-->
 +
 +
==Contributing or Reviewing Work Groups==
 +
 +
<!-- Additional work groups that may have an interest in contributing to, or reviewing  the content of the IG (optional) -->
 +
* Work Group Name
 +
* or link
 +
* or "None"
 +
 +
==FHIR Development Project Insight ID==
 +
 +
<!-- Please specify the id of your work group’s PSS for doing FHIR work that covers the development and maintenance of this IG.  (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 -->
 +
 +
==Scope of coverage==
 +
 +
<!-- Define the full scope of coverage for the IG.  **(NOT the project - Do NOT copy from the PSS)**  The scope must be clearly delineated such that it does not overlap with any other existing or expected HL7 Int'l-maintained IG.  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%".  Essentially, set the boundaries that would determine whether new content brought to HL7 should fall within the scope of your IG or somewhere else.  This should be 1 paragraph max.
 +
 +
Scope should consider numerous aspects of breadth of scope, including:
 +
* 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
 +
-->
 +
 +
==Content location==
 +
 +
<!-- What is the path within the HL7 github repository (i.e. https://github.com/HL7/xxx) or what is the Simplifier project name? -->
 +
 +
 +
==Proposed IG realm and code==
 +
 +
<!-- What is the realm code (2-character country code or 'uv') and IG code to use for the path when the IG is published under http://hl7.org/fhir?  E.g. us/ccda -->
 +
 +
==Maintenance Plan==
 +
 +
<!-- What commitment does the WG have to maintaining this IG as the FHIR core specification continues to evolve - particularly if the initial project sponsors are no longer providing resources.  I.e. Who will be maintaining this IG content 5 years after it's published? -->
 +
 +
==Short Description==
 +
 +
<!-- 1-2 sentences describing the purpose/scope of the IG for inclusion in the registry- this is the sentence that will be used here: http://www.fhir.org/guides/registry.  This must describe the IG from the perspective of an implementer scanning a registry, it should not talk about the project and should NOT be copied from the PSS. -->
 +
 +
 +
==Long Description==
 +
 +
<!-- 1-2 paragraphs describing the purpose/scope of the IG in more detail for inclusion in the version history - this is content that will be used in your IG's equivalent of this: http://www.hl7.org/fhir/us/core/history.cfml.  Again, this must describe the IG from the perspective of an implementer scanning a registry, it should not talk about the project and should NOT be copied from the PSS. -->
 +
 +
 +
==Involved parties==
 +
 +
<!-- 1 paragraph describing who is sponsoring or involved in creating the IG **for inclusion in the version history**.  Don't copy from the PSS - think about the specific language you want to appear in the registry. -->
 +
 +
 +
==Expected implementations==
 +
 +
<!--Provide named implementations if possible - ideally provide multiple independent implementations. -->
 +
 +
==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
 +
 +
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? -->
 +
 +
==Example Scenarios==
 +
 +
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this IG.  They should demonstrate the full scope of the IG and allow exercising of the IG's capabilities (all profiles, different types of applications, etc.) -->
 +
 +
==IG Relationships==
 +
 +
<!-- Are there any IGs this resource depends on or that depend on this IG? -->
 +
 +
==Timelines==
 +
 +
<!-- Indicate the target date for having the IGcomplete from a committee perspective and ready for vetting and voting -->
 +
 +
==When IG Proposal Is Complete==
 +
'''When you have completed your proposal, please send an email to [mailto:FMGcontact@HL7.org FMGcontact@HL7.org]'''
 +
 +
==FMG Notes==

Latest revision as of 20:16, 23 July 2019

Breast Radiology Logical Models and FHIR® Profiles:

Owning work group name: Clinical Interoperability Council

Contributing or Reviewing Work Groups:

   HL7 Clinical Interoperability Council (CIC)
   HL7 Clinical Information Modeling Initiative (CIMI)
   HL7 Imaging Integration / DICOM 

FHIR Development Project Insight ID: 1363

Scope of coverage:

The breast radiology implementation guide intends to formalize the radiology-specific data-elements sufficient to support breast cancer diagnosis, treatment and research, focusing on the key data necessary to facilitate clinical decision-making for medical and surgical oncologists, pathologists and the referring physician community of general practices Obstetrics and gynecology (OB/GYN) clinicians who order the vast majority of screening mammography procedures.

The implementation guide is expected to incrementally cover a wide variety breast radiology use cases, while supporting secondary data use in for clinical research, cancer registry reporting.

IG Purpose:

The purpose of this implementation guide is to provide detailed CIMI clinical models, and FHIR Profiles required to facilitate reliable and consistent capture and exchange of interoperable medical records in the breast radiology domain. Applications such as clinical decision support, clinical quality measures, evidence-based and precision medicine all require a standardized specification for computable data elements (aka clinical models). This implementation guide will provide FHIR-based representations of standardized breast radiology data to support these applications.

Content location

We already have content into the HL7 GitHub repository: https://github.com/HL7/fhir-breast-radiology-ig

Proposed IG realm and code: us/breast-radiology

Maintenance and Development Plan:

The CIC WG is aware and willing to maintain the content in the future. Among participants, at least MITRE, MRS and PenRad are committed to the maintenance of the content.

This IG comprises CIMI logical models and FHIR Profiles for breast radiology core data elements long established to be critical for breast cancer diagnosis and staging within the scope of radiology.

In the first 'For Comment' cycle the terminology bindings are preliminary, and in some cases, defined in terms of local codes only.

Our team is collaborating with the VA SOLOR groups, RSNA RadLex and Regenstrief (LOINC) to organize and fund the required unique concept authoring efforts that will be necessary to sufficiently define the data-elements and value-sets represented in the 'For Comment' and 'Informative' breast-radiology draft ballot cycles.

Short Description: Breast Radiology CIMI Logical Models and FHIR Profiles.

Long Description:

The first iteration of the CIMI logical models and FHIR Profiles for breast radiology reporting will be focused on the core modeling structures, patterns and informational relationships between these architectural elements. Our group has works extensively with the HL7 Orders and Observations workgroup to investigate the numerous 'cross cutting' concerns that

This IG defines logical models and FHIR profiles for data elements that are either directly or indirectly used in the reporting of breast radiology.

Involved parties:

The breast-radiology IG is being authored through a formal collaboration under the HL7-CIC workgroup with a wide range of organizations and individual contributors that informally refer the themselves as the 'Cancer Interoperability' Group, which includes representatives from the FDA, NIH, CCO, SBI, HSPC, CiiC, ACS, various health IT vendors and interested solution vendors.

The American College of Radiology (ACR) has will established and long standing guidelines that have been in common and broad use for almost two decades. The Radiological Society of North America (RSNA) and the Society of Breast Imaging (SBI) which the breast focused arm of the ACR are all represented on the subject matter expert team that is reviewing all content and will be used as the definitive source of truth for all our near-term deliverables.

Committed implementors include the MITRE Corporation, PenRad Inc, MRS Inc. and Intermountain Healthcare.

Expected implementations:

MITRE's Standard Health Record Collaborative, PenRad and Mammography Reporting System, inc (MRS). PenRad and MRS represent well over fifty percent of the almost forty million screening mammography studies performed each year. PenRad and MRS are also committed to participating in FHIR Connectathons to proof the draft profiles.


Specifications consulted for the development of this IG include:

   American College of Radiology Breast Reporting Guidelines 
   College of American Pathology (CAP) Breast Reporting SDC Forms
   Society of Breast Imaging Reporting Guidelines
   In addition to sources specifically providing clinical content related to cancer and breast cancer, from a modeling perspective, CIMI models were also used as a source.

Example Scenarios:

   Capture and delivery of breast radiology reports to EHR systems
   Reporting to cancer registries
   Reporting for clinical trials
   IG Relationships:  
   The breast-radiology project is intended to target compliance with  US Core v4.

Timelines:

   For Comment September 2019 Ballot
   Informative Jan 2020 Ballot
   STU May 2020 Ballot




PutProposedIGNameHere

Owning work group name

YourWorkGroupName

Committee Approval Date:

Please enter the date that the committee approved this IGproposal

Publishing Lead

Contributing or Reviewing Work Groups

  • Work Group Name
  • or link
  • or "None"

FHIR Development Project Insight ID

Scope of coverage

Content location

Proposed IG realm and code

Maintenance Plan

Short Description

Long Description

Involved parties

Expected implementations

Content sources

Example Scenarios

IG Relationships

Timelines

When IG Proposal Is Complete

When you have completed your proposal, please send an email to FMGcontact@HL7.org

FMG Notes