Difference between revisions of "BirthDefectsReporting FHIR IG Proposal"

From HL7Wiki
Jump to navigation Jump to search
 
(18 intermediate revisions by 2 users not shown)
Line 3: Line 3:
 
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
<div style="background:#F0F0F0">
 
<div style="background:#F0F0F0">
This page documents a [[:category:Pending FHIR IG Proposal|Pending]] [[:category:FHIR IG Proposal|FHIR IG Proposal]]
+
This page documents a [[:category:Approved FHIR IG Proposal|Approved]] [[:category:FHIR IG Proposal|FHIR IG Proposal]]
 
</div>
 
</div>
 
</div>
 
</div>
 
[[Category:FHIR IG Proposal]]
 
[[Category:FHIR IG Proposal]]
[[Category:Pending FHIR IG Proposal]]
+
[[Category:Approved FHIR IG Proposal]]
  
  
Line 32: Line 32:
  
 
==Committee Approval Date:==
 
==Committee Approval Date:==
<i>Please enter the date that the committee approved this IGproposal</i>
+
WG approval: May 16 2019
 +
 
 +
FMG approval: May 22 2019
 +
 
 +
Clinical SD approval: June 3 2019
  
 
==Publishing Lead==
 
==Publishing Lead==
 
+
Craig Newman - craig.newman_at_altarum.org
 
<!--Name and email of the primary contact for the FMG with respect to publishing for this IG?-->
 
<!--Name and email of the primary contact for the FMG with respect to publishing for this IG?-->
  
Line 41: Line 45:
  
 
<!-- Additional work groups that may have an interest in contributing to, or reviewing  the content of the IG (optional) -->
 
<!-- Additional work groups that may have an interest in contributing to, or reviewing  the content of the IG (optional) -->
* Work Group Name
+
None
* or link
 
* or "None"
 
  
 
==FHIR Development Project Insight ID==
 
==FHIR Development Project Insight ID==
 
+
Project ID 1532
 
<!-- 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 -->
 
<!-- 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==
 
==Scope of coverage==
 +
This proposal covers the reporting of birth defects for human patients up to the age of 12 years in the United States. Reporting is from a provider in either a hospital or ambulatory location to a jurisdictional birth defect registry. Reporting may happen at the time of birth or any time afterwards if a birth defect is diagnosed later. Content for reporting includes demographics and vital records content for the individual, family/social context, pregnancy/delivery information and also specific clinical content related to the birth defect(s) for the patient.
  
 
<!-- 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.
 
<!-- 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.
Line 61: Line 64:
  
 
==Content location==
 
==Content location==
 
+
TBD - is there a suggested github repository pathway?
 
<!-- What is the path within the HL7 github repository (i.e. https://github.com/HL7/xxx) or what is the Simplifier project name? -->
 
<!-- 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==
 
==Proposed IG realm and code==
 
+
us/birthdefectreporting
 
<!-- 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 -->
 
<!-- 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==
 
==Maintenance Plan==
 
+
Altarum works with the state of Michigan to develop and support their birth defect registry. This association is expected to continue after the publication of the IG.
 
<!-- 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? -->
 
<!-- 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==
 
==Short Description==
 +
The purpose of the Birth Defects Reporting FHIR IG is to provide guidance on reporting birth defects, either at the time of birth or afterwards, from a provider to a jurisdictional birth defects registry. The IG covers reporting requirements from both the ambulatory and hospital contexts.
  
 
<!-- 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. -->
 
<!-- 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==
 +
The scope of this project is to produce and ballot a Standard for Trial Use (STU) Fast Healthcare Interoperability Resources (FHIR) implementation guide (IG) for use in reporting of birth defects in the U.S. to jurisdictional birth defect registries. Automation of the reporting process adds efficiencies that dramatically improves the efficacy of collecting data related to birth defects and patient outcomes.
  
==Long Description==
+
The clinical content being exchanged will be derived from a birth defects domain analysis model (which itself is an extension of a vital records domain analysis model). Content areas include patient demographics, related persons (mother, father), labor and delivery events and patient conditions (birth defects). Reporting is covered not only at the time of birth, but also through later stages of childhood.
  
 
<!-- 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. -->
 
<!-- 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==
 
==Involved parties==
 
+
The project is being sponsored by the state of Michigan but will include input from a variety of other jurisdictions as well as Health IT developers.
 
<!-- 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. -->
 
<!-- 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==
 
==Expected implementations==
 
+
The state of Michigan is expected to implement this IG in conjunction with healthcare organizations in the state.
 
<!--Provide named implementations if possible - ideally provide multiple independent implementations. -->
 
<!--Provide named implementations if possible - ideally provide multiple independent implementations. -->
  
 
==Content sources==
 
==Content sources==
 
+
The Birth Defects domain analysis model will be the primary source of clinical content. The development of this DAM will consult the existing Vital Records DAM and reuse components where possible. Where requirements overlap, the US Core FHIR profiles will be used to directly or as the basis for developing unique birth defect reporting profiles.
 
<!-- List all of the specifications (beyond those in the "standard" (FHIR_Design_Requirements_Sources) list of source specifications) that you’re planning to consult
 
<!-- List all of the specifications (beyond those in the "standard" (FHIR_Design_Requirements_Sources) list of source specifications) that you’re planning to consult
  
Line 99: Line 104:
  
 
==Example Scenarios==
 
==Example Scenarios==
 
+
Example scenarios include:
 +
1) reporting of a newborn birth defect at the time of birth from a hospital context
 +
2) reporting a birth defect identified later in life (during childhood) from an ambulatory (or hospital outpatient) context
 
<!-- 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.) -->
 
<!-- 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==
 
==IG Relationships==
 
+
This IG may overlap in patient-centric content with the vital records death reporting IG. Where possible, the two IGs will be harmonized. The IG will also use R4 US Core profiles where possible.
 
<!-- Are there any IGs this resource depends on or that depend on this IG? -->
 
<!-- Are there any IGs this resource depends on or that depend on this IG? -->
  
 
==Timelines==
 
==Timelines==
 
+
Work on the IG will begin in early 2020
 +
The anticipated ballot target date is September 2020 (meeting the standard FHIR IG deadlines for that ballot cycle)
 +
Ballot reconciliation will happen in the fall of 2020
 +
A publication date is expected in late 2020 or early 2021
 
<!-- Indicate the target date for having the IGcomplete from a committee perspective and ready for vetting and voting -->
 
<!-- Indicate the target date for having the IGcomplete from a committee perspective and ready for vetting and voting -->
  

Latest revision as of 18:25, 17 September 2019



Birth Defect Reporting FHIR IG

Owning work group name

Public Health

Committee Approval Date:

WG approval: May 16 2019

FMG approval: May 22 2019

Clinical SD approval: June 3 2019

Publishing Lead

Craig Newman - craig.newman_at_altarum.org

Contributing or Reviewing Work Groups

None

FHIR Development Project Insight ID

Project ID 1532

Scope of coverage

This proposal covers the reporting of birth defects for human patients up to the age of 12 years in the United States. Reporting is from a provider in either a hospital or ambulatory location to a jurisdictional birth defect registry. Reporting may happen at the time of birth or any time afterwards if a birth defect is diagnosed later. Content for reporting includes demographics and vital records content for the individual, family/social context, pregnancy/delivery information and also specific clinical content related to the birth defect(s) for the patient.


Content location

TBD - is there a suggested github repository pathway?


Proposed IG realm and code

us/birthdefectreporting

Maintenance Plan

Altarum works with the state of Michigan to develop and support their birth defect registry. This association is expected to continue after the publication of the IG.

Short Description

The purpose of the Birth Defects Reporting FHIR IG is to provide guidance on reporting birth defects, either at the time of birth or afterwards, from a provider to a jurisdictional birth defects registry. The IG covers reporting requirements from both the ambulatory and hospital contexts.


Long Description

The scope of this project is to produce and ballot a Standard for Trial Use (STU) Fast Healthcare Interoperability Resources (FHIR) implementation guide (IG) for use in reporting of birth defects in the U.S. to jurisdictional birth defect registries. Automation of the reporting process adds efficiencies that dramatically improves the efficacy of collecting data related to birth defects and patient outcomes.

The clinical content being exchanged will be derived from a birth defects domain analysis model (which itself is an extension of a vital records domain analysis model). Content areas include patient demographics, related persons (mother, father), labor and delivery events and patient conditions (birth defects). Reporting is covered not only at the time of birth, but also through later stages of childhood.


Involved parties

The project is being sponsored by the state of Michigan but will include input from a variety of other jurisdictions as well as Health IT developers.


Expected implementations

The state of Michigan is expected to implement this IG in conjunction with healthcare organizations in the state.

Content sources

The Birth Defects domain analysis model will be the primary source of clinical content. The development of this DAM will consult the existing Vital Records DAM and reuse components where possible. Where requirements overlap, the US Core FHIR profiles will be used to directly or as the basis for developing unique birth defect reporting profiles.

Example Scenarios

Example scenarios include: 1) reporting of a newborn birth defect at the time of birth from a hospital context 2) reporting a birth defect identified later in life (during childhood) from an ambulatory (or hospital outpatient) context

IG Relationships

This IG may overlap in patient-centric content with the vital records death reporting IG. Where possible, the two IGs will be harmonized. The IG will also use R4 US Core profiles where possible.

Timelines

Work on the IG will begin in early 2020 The anticipated ballot target date is September 2020 (meeting the standard FHIR IG deadlines for that ballot cycle) Ballot reconciliation will happen in the fall of 2020 A publication date is expected in late 2020 or early 2021

When IG Proposal Is Complete

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

FMG Notes