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

Difference between revisions of "FHIR Connectathon 16"

From HL7Wiki
Jump to navigation Jump to search
 
(31 intermediate revisions by 11 users not shown)
Line 1: Line 1:
−
[[Category:FHIR Connectathon Track Proposals|2s]]
+
[[Category:FHIR Connectathons]]
−
Sub category of [[:Category:FHIR Connectathon Track Proposals|FHIR Connectathon Track Proposals]] for the current connectathon: September 2017 [[FHIR_Connectathon_15|Connectathon 15]]
+
== Introduction ==
 +
(This page is under construction and contains information that is still subject to update and correction.)
 +
This page describes the Sixteenth FHIR Connectathon that will be held on Saturday Sept. 9 and the morning  of Sunday Sept. 10, 2017 in San Diego, CA, USA prior to the [http://www.hl7.org/events/working_group_meeting/2017/09/ Sept. HL7 Working Group Meeting].
 +
 
 +
===Location===
 +
 
 +
The meeting will be held at the host hotel, Hyatt Regency La Jolla at Aventine.
 +
 
 +
== Important notes:==
 +
 
 +
* '''Please note lunch is included for Sunday with the Connectathon registration fee.
 +
'''
 +
* Connectathon Demonstration Meeting Link: https://www.gotomeet.me/LloydMcKenzie
 +
 
 +
== Tracks ==
 +
 
 +
The following are the tracks for the Connectathon. Each item links to the original proposal, with the coordinators name and email on the linked page. View the link for details.
 +
 
 +
*[http://wiki.hl7.org/index.php?title=201709_CDS_Hooks CDS Hooks]
 +
*[http://wiki.hl7.org/index.php?title=201709_Clinical_Research Clinical Research]
 +
*[http://wiki.hl7.org/index.php?title=201709_Clinical_Reasoning Clinical Reasoning]
 +
*[http://wiki.hl7.org/index.php?title=201709_Consumer_Centered_Data_Exchange Consumer Centered Data Exchange]
 +
*[http://wiki.hl7.org/index.php?title=201709_DevicesOnFHIR  Devices on FHIR]
 +
*[http://wiki.hl7.org/index.php?title=201709_Genomics Genomics]
 +
*[http://wiki.hl7.org/index.php?title=201709_Implantables_Tracking Implantables Tracking]
 +
*[http://wiki.hl7.org/index.php?title=201709_LastN_Query_Track LastN Query track]
 +
*[http://wiki.hl7.org/index.php?title=201709_MHD_STU3 MHD STU3]
 +
*[http://wiki.hl7.org/index.php?title=201709_Patient_Reported_Observations Patient Reported Observations]
 +
*[http://wiki.hl7.org/index.php?title=201709_Patient_Track Patient Track (not just for beginners)]
 +
*[http://wiki.hl7.org/index.php?title=201709_Provider_Directories_and_Scheduling Provider Directories & Scheduling]
 +
*[http://wiki.hl7.org/index.php?title=201709_Terminology_Services_Track Terminology Services track]
 +
*[http://wiki.hl7.org/index.php?title=201709_Attachments Attachments]
 +
*[http://wiki.hl7.org/index.php?title=201709_Care_Plan Care Plan]
 +
*[http://wiki.hl7.org/index.php?title=201709_FHIR_Documents FHIR Documents]
 +
*[http://wiki.hl7.org/index.php?title=201709_FHIR_Subscriptions FHIR Subscriptions]
 +
*[http://wiki.hl7.org/index.php?title=201709_Financial_Management Financial Management]
 +
*[http://wiki.hl7.org/index.php?title=201709_ProcedureRequest Procedure Request]
 +
 
 +
=== Outcomes ===
 +
 
 +
 
 +
[https://docs.google.com/spreadsheets/d/1BoJHpwneS48kZO-uUXpP2ADZATaqPlkg7vg8M5xOMLA/edit?usp=sharing Link to the tracking spreadsheet]
 +
 
 +
== Connectathon Organization ==
 +
 
 +
The connectathon will be held over 2 days - the Saturday and Sunday prior to the HL7 Working Group Meeting.
 +
 
 +
It will be based on the STU3 version of the spec - located [here http://hl7.org/fhir/STU3/index.html].
 +
 
 +
Saturday is a full day, and is intended for participants to test and develop software in an informal way. Test servers will be available (actually, they are already - '''[http://wiki.hl7.org/index.php?title=Publicly_Available_FHIR_Servers_for_testing FHIR Test Servers]'''  ), but some participants may bring other servers along depending on the actors they are fulfilling.
 +
Sunday is the morning only, and has 2 parts:
 +
 
 +
* the formal testing part
 +
* a mini-showcase where the track leads can demonstrate representative work to the others
 +
 
 +
Each stream has a coordinator. The nominated coordinator's [http://wiki.hl7.org/index.php?title=Connectathon_Track_Lead_Responsibilities responsibilities]:
 +
* In the lead up to the connectathon: track participants, respond to queries about scenarios, connect participants to each other
 +
* During the connectathon act as a test mediator / progress tracker
 +
* track emergent issues that should be fed back to the committees
 +
 
 +
== Connectathon Planning Team ==
 +
*[mailto:david.hay25@gmail.com David Hay], Orion Health
 +
*[mailto:brian.pech@kp.org Brian Pech], Kaiser Permanente
 +
*[mailto:grahame@healthintersections.com.au Grahame Grieve], Health Intersections Pty Ltd
 +
 
 +
= Enrollment =
 +
 
 +
If you or your company are interested in participating in the connectathon, please do the following.
 +
*Read the '''[http://hl7-fhir.github.io/index.html Connectathon version of the FHIR Specification]''' and the '''[[ FHIR | FHIR wiki ]]''' if you haven't already done so, to become familiar with the concepts.
 +
*Read the '''scenario descriptions''' below. 
 +
*[http://www.hl7.org/events/working_group_meeting/2017/09/ Register to attend the WGM], and make sure to select the Connectathon option when you do
 +
*Optionally (but highly recommended) fill in the tracks and roles in which you are intending to participate in the spreadsheet (Note: link to be supplied)
 +
 +
Space at the venue is limited, so please register as soon as possible. Preference will be given to those who are actually participating in the technical event, but observers are welcome if space permits.
 +
 
 +
For any queries, either contact a member of the planning team, or post your question in the [http://lists.hl7.org/fhir FHIR list server]
 +
 
 +
== Registered Participants ==
 +
 
 +
[https://docs.google.com/spreadsheets/d/1wkOBIuR-q_IbBcc8uc3zeT1kivC_7_j5KDVf8unjIfE/edit?usp=sharing Link to sign up spreadsheet]
  
−
Proposals due by : June 7, 2017
 
  
−
Go to prior connectathon proposals: [[:Category:201701 FHIR Connectathon Track Proposals|May 2017 Connectathon Proposals]]
+
== Test servers ==
 +
(Note: link to be supplied)
  
−
Use this page to submit proposals for tracks for inclusion in the , 2017 connectathon.  These proposals will be reviewed and prioritized by the FMG as per the [[FHIR_Connectathon_Track_Process]].
 
  
−
[[FHIR|Return to the FHIR Main Page]]
+
These are the STU3 servers we are aware of:
 +
* Health Intersections:  http://test.fhir.org/r3
 +
* HAPI / University Health Network:  http://fhirtest.uhn.ca/baseDstu3
 +
* Vonk: http://vonk.furore.com
 +
* AEGIS.net, Inc.: http://wildfhir.aegis.net/fhir3-0-1
 +
* Telstra Health(HealthConnex): http://sqlonfhir-stu3.azurewebsites.net/fhir
 +
* Knapp Consulting Inc.: http://www.pknapp.com:8081/con13 (Financial Track)
 +
* Apelon (Most recent build): http://fhir.ext.apelon.com:7080/dtsserverws/fhir and Demo Page at http://fhir.ext.apelon.com:7080/DtsOnFhirDemo/logon/Logon.action
 +
**Through a collaboration with the American Medical Association, the Current Procedural Terminology (CPT®) is now available for use in FHIR development efforts through the Apelon DTS on FHIR® service. Authentication is required. Please send an email to support@apelon.com for a user/pass. Please note that use of CPT® for production or commercial purposes through this service is prohibited.
 +
* HSPC: http://sandbox.hspconsortium.org
  
−
__NOTOC__
+
= Should I come only for the Connectathon? =
−
=FHIR Genomics=
+
Coming for the connectathon alone has value - many implementers have attended just for the Saturday/Sunday and been happy.  However, if you're already on-site, there's a lot of other FHIR-related activities to participate in that may further increase your return on investment (see the list of tutorials at the bottom of this page)
  
−
==Submitting WG/Project/Implementer Group==
+
== FHIR User Group ==
−
<!-- Who is asking for this track? -->
+
Subsequent to the actual connectathon (i.e. Sunday PM) the "[[AID|Application Implementation and Design (AID)]]" HL7 User Group will meet to discuss FHIR implementation approaches and design patterns. You're invited to share your 'lessons learned' with others in the FHIR implementation community, or to listen to other FHIR implementers.
−
[[CG]]
+
*See [[AID 201709 Meeting in San Diego|AID Sunday PM Agenda]] for details.
 +
*Please contact [mailto:andy.stechishin@gmail.com Andy Stechishin] to get hold of a slot on the AID agenda - we do appreciate you sharing your ideas and experiences.
  
−
==Justification==
+
== FHIR Tutorials ==
−
<!--Why is this an important track to include in the connectathon - include implementer need, impact on ballot, FMM readiness of the resources, etc. -->
+
*There are 9 FHIR tutorials scheduled through-out the week
−
Genomic data are of increasing importance to clinical care and secondary analysis. Please see [http://www.ncbi.nlm.nih.gov/pubmed/26198304 this recent JAMIA article] for a primer on some of the work to date on bringing genomic data definitions into the FHIR specification. FHIR Genomics consists of the Sequence resource and several profiles built on top of existing FHIR resources (DiagnosticReport-genetics profile, DiagnosticOrder-genetics profile, Observation-genetics profile). The Sequence resource is a core resource in FHIR Genomics. It is used to represent complex genetics data. FHIR Genomics focuses on clinical genetics data reporting.
+
*(Mon. PM) Introduction to HL7 FHIR
 +
*(Mon. PM) HAPI on FHIR
 +
*(Tues. AM) FHIR for Architects
 +
*(Tues. PM) FHIR for Specifiers
 +
*(Tues. PM) Driving Health Information Exchange Using XDS with CDA and FHIR
 +
*(Wed. AM) Introduction to FHIR Development
 +
*(Wed. AM) FHIR Proficiency Exam Preparation
 +
*(Wed. PM) Understanding and Using Terminology in HL7 FHIR
 +
*(Thur. AM) C-CDA on FHIR  
 +
*(Thur. PM) Precision Medicine via FHIR: From Design to Deployment
  
−
==Proposed Track Lead==
+
Detailed descriptions are available in the [http://www.hl7.org/events/working_group_meeting/2017/09/tutorials.cfm Event brochure]
−
<!-- Name, email and Skype id of individual who will coordinate the track at the connectathon -->
 
−
[mailto:gilusa@gmail.com Gil Alterovitz]
 
  
−
==Report==
+
== FHIR Proficiency Exam ==
−
[http://www.slideshare.net/DavidHay5/genomics-connectathon Report]
 
  
−
==Expected participants==
+
*The FHIR proficiency test allows test takers to demonstrate their knowledge and understanding of the specification.  This is a basic proficiency test, not a professional credentialing test.  It will be multiple choice, multi-select, and true/false and based on the STU3 specification and not on field knowledge. Those who pass the test will receive the FHIR Proficiency Certificate, a Certificate of Knowledge.
−
<!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track -->
 
  
−
Gil Alterovitz - HMS/BCH
+
*There will be a tutorial to help prepare for the exam:
 +
** (Wed. AM) FHIR Proficiency Exam Preparation
  
−
Bob Milius - NMDP
+
*The exam will be held on Thursday in the afternoon.
  
−
Martin Maiers - NMDP
+
== Working Group session ==
 +
HL7 WGMs are where a lot of the development work on FHIR happens.  Numerous work groups will be considering FHIR change proposals, working on FHIR profiles and resources and debating other aspects of FHIR implementation.  As well, there will be meetings of the [[FHIR Governance Board]] and [[FHIR Management Group]] discussing policies relating to FHIR.  There are often ad-hoc meetings at breakfast, lunch and after-hours to discuss items of interest such as tooling, new domains, particular technical issues, etc.
  
−
Cat Lasome - iON Informatics
+
The final agenda won't be determined until very close to the meeting (and will evolve somewhat throughout the course of the week), however you can take a look at the [[http://wiki.hl7.org/index.php?title=FHIR_Agenda_2014605_WGM|agenda]] from the May 2014 WGM to get a sense of the breadth of discussions that will be taking place.  FHIR runs full bore from Monday to Friday (capping off with the clinical connectathon on Friday), so regardless of what days you're present, there will likely be something of interest.
  
−
Grant Wood - Intermountain Healthcare
+
Participating in the WGM is a good way to get a sense of the people involved in building the spec, to form relationships, to get more deeply involved in the FHIR community and to influence how the standard evolves.
  
−
Joel Schneider - NMDP
+
= Outcomes (for coordinators) =
  
−
Shennon Lu - National Library of Medicine
+
The following outcomes will be recorded for each track
  
−
==Roles==
+
=== Results by track ===
−
===FHIR Client===
+
how many completed each track - clients & servers
−
Support the sending of the Sequence resource/genetics profiles operations: create, history, read, search and update.
 
  
−
===FHIR Server===
+
=== Key learnings ===
−
Support the receiving and processing of the Sequence resource/genetics profiles operations: create, history, read, search and update.
+
what changes to the spec resulted from the connectathon?
  
−
==Scenarios==
+
=== Changes next time ===
−
<!-- What will be the actions performed by participants? -->
+
Does the track need to be repeated next time? (Remember, there are lots to do!)
−
Scenarios 2-6 are taken from use cases in the [HL7 Domain Analysis Model (DAM): Clinical Genomics, Release 1, September 2014 Informative Ballot].  See links below each scenario for relevant DAM excerpts.
+
If so, what would be changed?
−
A couple new use cases may be considered as approved by CG workgroup and time permits.
 
  
−
===Scenario 1 Register a New Sequence and Observation===
+
=== Overall comments ===
−
:Action: (FHIR Client) (FHIR Client) Create a sequence instance and a genetic-profile-based observation instance to represent genetics data and interpretations (DNA variant, RNA sequence, structural variant, etc). <!--Who does what?  (Use the role names listed above when referring to the participants -->
+
anything else - what worked, what didn't
−
:Precondition: The sequence instance and observation instance do not exist in service prior to action. <!-- What setup is required prior to executing this step? -->
+
could the overall organization be changed
−
:Success Criteria: Sequence and observation instances created correctly on server and in the desired format. <!-- How will the participants know if the test was successful? -->
 
−
:Bonus point: New profiles can be built on top of the Sequence resource for complex representation<!-- Any additional complexity to make the scenario more challenging -->
 
−
<!-- Provide a description of each task -->
 
  
−
===Scenario 2 Clinical Sequencing - Germline Testing===
 
−
[https://docs.google.com/document/d/1-PULyIwtpCZmsANpafzYA2CKJ1ZMiIysdNnFoGf2-KY/edit#heading=h.gjdgxs?usp=sharing/ More on Scenario 2]
 
−
:Action: (FHIR Client) Search target genetic-profile-based observation with given patient ID. This target observation has an extension - Genomic Source Class (url: http://hl7.org/fhir/StructureDefinition/observation-geneticsGenomicSourceClass
 
−
) and the value is germline (code: LA6683-2).
 
−
:Precondition: Relevant patient and observations have been created
 
−
:Success Criteria: A bundle of genetics observations from germline analysis of that patient are returned.<!-- How will the participants know if the test was successful? -->
 
−
:Bonus point: More parameters can be added for searching<!-- Any additional complexity to make the scenario more challenging -->
 
  
−
===Scenario 3 Family Member History===
+
= Other References =
−
[https://docs.google.com/document/d/1-PULyIwtpCZmsANpafzYA2CKJ1ZMiIysdNnFoGf2-KY/edit#heading=h.3dy6vkm?usp=sharing/ More on Scenario 3]
 
−
:Action: (FHIR Client) 1. Search the genetics diagnostic reports of a given patient.  Get the reference id of this patient’s familymemberhistory from extension - Family History (url: http://hl7.org/fhir/StructureDefinition/DiagnosticReport-geneticsFamilyMemberHistory
 
−
). 2. Retrieve this FamilyMemberHistory instance and get the reference id of Observation instances from extension - Genetic markers, ethnicity, etc.
 
−
(url: http://hl7.org/fhir/StructureDefinition/family-member-history-genetics-observation). 3. Retrieve the target Observation instance.
 
−
:Precondition: Relevant diagnostic report, observation, family member history have been created.
 
−
:Success Criteria: The target Observation instances of the given patient's family member are returned.<!-- How will the participants know if the test was successful? -->
 
−
:Bonus point: More parameters can be added for searching<!-- Any additional complexity to make the scenario more challenging -->
 
  
−
===Scenario 4 Clinical and Research Data Warehouses===
+
* Other FHIR Connectathons:
−
[https://docs.google.com/document/d/1-PULyIwtpCZmsANpafzYA2CKJ1ZMiIysdNnFoGf2-KY/edit#heading=h.4d34og8?usp=sharing/ More on Scenario 4]
+
** 1st [[FHIR Connectathon]] (8 Sept. 2012 - Baltimore MD, USA)
−
:Action: (FHIR Client) Search for all genetic-profile-based observations with a given variant (e.g. rs587778247)
+
** [[FHIR Connectathon 2]] (12/13 Jan. 2013 - Phoenix AZ, USA)
−
:Precondition: Observation instances with this variant have been created
+
** [[FHIR Connectathon 3]] (4/5 May 2013 - Atlanta GA, USA)
−
:Success Criteria: A bundle of genetics observations, where the code value of extension - Variant Id (url: http://hl7.org/fhir/StructureDefinition/observation-geneticsDNAVariationId
+
** [[FHIR Connectathon 4]] (21/22 Sept. 2013 - Cambridge MA, USA)
−
) is rs587778247. <!-- How will the participants know if the test was successful? -->
+
** FHIR Mini Connectathon (Oct. 2013 - Sydney, Australia)
−
:Bonus point: More parameters can be added for searching<!-- Any additional complexity to make the scenario more challenging -->
+
** [[FHIR Connectathon 5]] (18/19 Jan. 2014 - San Antonio TX, USA)
 +
** [[FHIR Connectathon 6]] (3/4 Jan. 2014 - Phoenix, Arizona, USA)
 +
** [[FHIR Connectathon 7]] (September. 2014 - Chicago, IL, USA)
 +
** [[FHIR Connectathon 8]] (January 2015 - San Antonio, TX, USA)
 +
** [[FHIR Connectathon 9]] (May 2015 - Paris, France)
 +
** [[FHIR Connectathon 11]] (Jan 2016 - Orlando, FL, USA)
 +
** [[FHIR Connectathon 12]] (May 2016 - Montreal, Canada)
 +
** [[FHIR Connectathon 13]] (September 2016 - Baltimore, MD, USA)
 +
** [[FHIR Connectathon 14]] (January 2017, San Antonio, USA)
 +
**[[FHIR  Connectathon 15]] (May 2017 - Madrid, Spain)
  
−
===Scenario 5 HLA Typing===
+
[[Category:FHIR Connectathons]]
−
[https://docs.google.com/document/d/1-PULyIwtpCZmsANpafzYA2CKJ1ZMiIysdNnFoGf2-KY/edit#heading=h.17dp8vu?usp=sharing/ More on Scenario 5]
 
−
:Action: (FHIR Client) Create an HLA genotyping genetics report.
 
−
:Precondition: This DiagnosticReport-hlaresults instance does not exist in service prior to action.
 
−
:Success Criteria: The HLA genetics report is created correctly on server and in the desired format.
 
−
:Bonus point: Extensions can be added<!-- Any additional complexity to make the scenario more challenging -->
 
  
−
===Scenario 6 Species Identification===
 
−
[https://docs.google.com/document/d/1-PULyIwtpCZmsANpafzYA2CKJ1ZMiIysdNnFoGf2-KY/edit#heading=h.tyjcwt?usp=sharing/ More on Scenario 6]
 
−
:Action: (FHIR Client) Search for sequences from human (Homo sapiens).
 
−
:Precondition: Sequence(s) have been created where the species is defined as human (Homo sapiens).
 
−
:Success Criteria: A bundle of Sequence instances where the value of the species element is Homo sapiens.
 
  
−
===Scenario 7 Comprehensive Pathology Report===
 
−
A comprehensive pathology report integrates pertinent information gathered from various methods (e.g. morphology, immunohistochemistry, flow cytometry, cytogenetics, fluorescence ''in situ'' hybridization [FISH], and molecular testing [e.g., NGS]). The DiagnosticReport-genetics profile has the capability to support results with simple or complex genetics observations.
 
−
:Action: (FHIR Client) Create a comprehensive pathology report which includes genetic information for a patient.
 
−
:Precondition: This diagnostic report has never been created
 
−
:Success Criteria: Sequence created correctly on server and in the desired format.
 
−
:Bonus point: Extensions can be added.
 
  
−
===Scenario 8 Sequence quality===
 
−
In the sequencing reads, each base is assigned with a quality score generated by the sequencer, which represents the confidence of a base call. Base quality is a critical factor for accurate variant detection in the downstream analysis.
 
−
:Action: (FHIR Client) Get the quality of the sequence under consideration.
 
−
:Precondition: This sequence instance has been created
 
−
:Success Criteria: Target sequence instance is returned.
 
−
:Bonus point: More parameters can be added for searching
 
  
−
===Scenario 9 Pharmocogenomics===
+
[[Category:FHIR Connectathon Track Proposals|2s]]
−
:Action: (FHIR Client)Search for TPMT-related genetic observations for given patient ID.
+
Sub category of [[:Category:FHIR Connectathon Track Proposals|FHIR Connectathon Track Proposals]] for the current connectathon: September 2017 [[FHIR_Connectathon_16|Connectathon 16]]
−
referenced by pharmacogenomics report.  Obtain diagnostic report that points to this observation.
 
−
:Precondition: Diagnostic report, observation(s), sequence(s) and the target patient instances are created.
 
−
:Success Criteria: Relevant diagnostic report that points to genetic observation(s) for TPMT
 
−
:Bonus point: Different parameters (such as genomic coordinates) can be used for searching
 
−
See IOM guide: Maybe be good to do one of the IOM variants.
 
−
http://www.nationalacademies.org/hmd/~/media/Files/Activity%20Files/Research/GenomicBasedResearch/Action%20Collaboratives/DIGITizE%20Abacavir%20and%20TPMT%20CDS%20Implementation%20Guide%20-%20Final%201_0.pdf?la=en
 
  
−
{|border="1" cellpadding="2" cellspacing="0"
+
Proposals due by : June 7, 2017
−
| width="30%" colspan="1" align="left" style="background:#f0f0f0;"|'''Element'''
 
−
| width="35%" colspan="1" align="left" style="background:#f0f0f0;"|'''Sequence #1'''
 
−
| width="35%" colspan="1" align="left" style="background:#f0f0f0;"|'''Sequence #2'''
 
−
|-
 
−
||variationID
 
−
||rs58238559
 
−
||rs58238560
 
−
|-
 
−
||coordinate.chromosome
 
−
||7
 
−
||7
 
−
|-
 
−
||coordinate.start
 
−
||87452957
 
−
||87082273
 
−
|-
 
−
||coordinate.end
 
−
||87452958
 
−
||87082274
 
−
|-
 
−
||coordinate.genomeBuild
 
−
||GRCh38.p2
 
−
||GRCh38.p2
 
−
|-
 
−
||gene
 
−
||ABCB4
 
−
||ABCB4
 
−
|-
 
−
||region
 
−
||Exon 23
 
−
||Exon 6
 
−
|-
 
−
||species
 
−
||human
 
−
||human
 
−
|-
 
−
||observedAllele
 
−
||T
 
−
||T
 
−
|-
 
−
||referenceAllele
 
−
||C
 
−
||A
 
−
|-
 
−
|}
 
−
===Observation-genetics===
 
  
−
{|border="1" cellpadding="2" cellspacing="0"
+
Go to prior connectathon proposals: [[:Category:201701 FHIR Connectathon Track Proposals|May 2017 Connectathon Proposals]]
−
| width="16%" colspan="1" align="left" style="background:#f0f0f0;"|'''Element'''
 
−
| width="28%" colspan="1" align="left" style="background:#f0f0f0;"|'''Observation #1'''
 
−
| width="28%" colspan="1" align="left" style="background:#f0f0f0;"|'''Observation #2'''
 
−
| width="28%" colspan="1" align="left" style="background:#f0f0f0;"|'''Observation #3'''
 
−
|-
 
−
||category
 
−
||complex
 
−
||complex
 
−
||simple
 
−
|-
 
−
||code
 
−
||49874-1: ABCB4 gene mutation analysis in Blood or Tissue by Molecular genetics method Narrative
 
−
||49874-1: ABCB4 gene mutation analysis in Blood or Tissue by Molecular genetics method Narrative
 
−
||54447-8: LT3 gene mutation analysis in Bone marrow by Molecular genetics method Narrative
 
−
|-
 
−
||subject
 
−
||Marry Chalmers
 
−
||Marry Chalmers
 
−
||Marry Chalmers
 
−
|-
 
−
||effectiveTime
 
−
||2015-3-11 10:28:00
 
−
||2015-3-11 10:28:00
 
−
||2015-3-10 11:05:00
 
−
|-
 
−
||issued
 
−
||2015-3-12 15:40:00
 
−
||2015-3-12 15:40:00
 
−
||2015-3-12 15:40:00
 
−
|-
 
−
||performer
 
−
||Molecular Diagnostic Laboratory 
 
−
||Molecular Diagnostic Laboratory
 
−
||Molecular Diagnostic Laboratory
 
−
|-
 
−
||value
 
−
||Positive
 
−
||Positive
 
−
||Positive
 
−
|-
 
−
||GeneticsSequence
 
−
||(refer to) Sequence #1
 
−
||(refer to) Sequence #2
 
−
||None
 
−
|}
 
  
−
===DiagnosticReport-genetics===
+
Use this page to submit proposals for tracks for inclusion in the , 2017 connectathon.  These proposals will be reviewed and prioritized by the FMG as per the [[FHIR_Connectathon_Track_Process]].
  
−
{|border="1" cellpadding="2" cellspacing="0"
+
[[FHIR|Return to the FHIR Main Page]]
−
| width="30%" colspan="1" align="left" style="background:#f0f0f0;"|'''Element'''
 
−
| width="70%" colspan="1" align="left" style="background:#f0f0f0;"|'''DiagnosticReport #1''
 
−
|-
 
−
||status
 
−
||final
 
−
|-
 
−
||code
 
−
||Comprehensive genetics report
 
−
|-
 
−
||subject
 
−
||Marry Chalmers
 
−
|-
 
−
||effectiveTime
 
−
||2015-3-11 10:28:00
 
−
|-
 
−
||issued
 
−
||2015-3-12 15:40:00
 
−
|-
 
−
||specimen
 
−
||Venous blood specimen
 
−
|-
 
−
||result
 
−
||Observation #1
 
−
|-
 
−
||result
 
−
||Observation #2
 
−
|-
 
−
||result
 
−
||Observation #3
 
−
|-
 
−
|}
 
  
−
==TestScript(s)==
+
[[FHIR_Genomics|FHIR Genomics]]
−
<!-- Optional (for initial proposal): Provide links to the TestScript instance(s) that define the behavior to be tested. 
 
−
These should be committed to SVN under trunk/connectathons/[connectathon]-->
 
−
The supporting TestScripts and corresponding fixtures have been committed to the FHIR SVN repository at:
 
−
http://gforge.hl7.org/svn/fhir/trunk/connectathons/BaltimoreSep2016/Connectathon13/FHIRGenomics
 

Latest revision as of 16:34, 3 January 2018

Introduction

(This page is under construction and contains information that is still subject to update and correction.) This page describes the Sixteenth FHIR Connectathon that will be held on Saturday Sept. 9 and the morning of Sunday Sept. 10, 2017 in San Diego, CA, USA prior to the Sept. HL7 Working Group Meeting.

Location

The meeting will be held at the host hotel, Hyatt Regency La Jolla at Aventine.

Important notes:

  • Please note lunch is included for Sunday with the Connectathon registration fee.

Tracks

The following are the tracks for the Connectathon. Each item links to the original proposal, with the coordinators name and email on the linked page. View the link for details.

Outcomes

Link to the tracking spreadsheet

Connectathon Organization

The connectathon will be held over 2 days - the Saturday and Sunday prior to the HL7 Working Group Meeting.

It will be based on the STU3 version of the spec - located [here http://hl7.org/fhir/STU3/index.html].

Saturday is a full day, and is intended for participants to test and develop software in an informal way. Test servers will be available (actually, they are already - FHIR Test Servers ), but some participants may bring other servers along depending on the actors they are fulfilling. Sunday is the morning only, and has 2 parts:

  • the formal testing part
  • a mini-showcase where the track leads can demonstrate representative work to the others

Each stream has a coordinator. The nominated coordinator's responsibilities:

  • In the lead up to the connectathon: track participants, respond to queries about scenarios, connect participants to each other
  • During the connectathon act as a test mediator / progress tracker
  • track emergent issues that should be fed back to the committees

Connectathon Planning Team

Enrollment

If you or your company are interested in participating in the connectathon, please do the following.

  • Read the Connectathon version of the FHIR Specification and the FHIR wiki if you haven't already done so, to become familiar with the concepts.
  • Read the scenario descriptions below.
  • Register to attend the WGM, and make sure to select the Connectathon option when you do
  • Optionally (but highly recommended) fill in the tracks and roles in which you are intending to participate in the spreadsheet (Note: link to be supplied)

Space at the venue is limited, so please register as soon as possible. Preference will be given to those who are actually participating in the technical event, but observers are welcome if space permits.

For any queries, either contact a member of the planning team, or post your question in the FHIR list server

Registered Participants

Link to sign up spreadsheet


Test servers

(Note: link to be supplied)


These are the STU3 servers we are aware of:

Should I come only for the Connectathon?

Coming for the connectathon alone has value - many implementers have attended just for the Saturday/Sunday and been happy. However, if you're already on-site, there's a lot of other FHIR-related activities to participate in that may further increase your return on investment (see the list of tutorials at the bottom of this page)

FHIR User Group

Subsequent to the actual connectathon (i.e. Sunday PM) the "Application Implementation and Design (AID)" HL7 User Group will meet to discuss FHIR implementation approaches and design patterns. You're invited to share your 'lessons learned' with others in the FHIR implementation community, or to listen to other FHIR implementers.

FHIR Tutorials

  • There are 9 FHIR tutorials scheduled through-out the week
  • (Mon. PM) Introduction to HL7 FHIR
  • (Mon. PM) HAPI on FHIR
  • (Tues. AM) FHIR for Architects
  • (Tues. PM) FHIR for Specifiers
  • (Tues. PM) Driving Health Information Exchange Using XDS with CDA and FHIR
  • (Wed. AM) Introduction to FHIR Development
  • (Wed. AM) FHIR Proficiency Exam Preparation
  • (Wed. PM) Understanding and Using Terminology in HL7 FHIR
  • (Thur. AM) C-CDA on FHIR
  • (Thur. PM) Precision Medicine via FHIR: From Design to Deployment

Detailed descriptions are available in the Event brochure

FHIR Proficiency Exam

  • The FHIR proficiency test allows test takers to demonstrate their knowledge and understanding of the specification. This is a basic proficiency test, not a professional credentialing test. It will be multiple choice, multi-select, and true/false and based on the STU3 specification and not on field knowledge. Those who pass the test will receive the FHIR Proficiency Certificate, a Certificate of Knowledge.
  • There will be a tutorial to help prepare for the exam:
    • (Wed. AM) FHIR Proficiency Exam Preparation
  • The exam will be held on Thursday in the afternoon.

Working Group session

HL7 WGMs are where a lot of the development work on FHIR happens. Numerous work groups will be considering FHIR change proposals, working on FHIR profiles and resources and debating other aspects of FHIR implementation. As well, there will be meetings of the FHIR Governance Board and FHIR Management Group discussing policies relating to FHIR. There are often ad-hoc meetings at breakfast, lunch and after-hours to discuss items of interest such as tooling, new domains, particular technical issues, etc.

The final agenda won't be determined until very close to the meeting (and will evolve somewhat throughout the course of the week), however you can take a look at the [[1]] from the May 2014 WGM to get a sense of the breadth of discussions that will be taking place. FHIR runs full bore from Monday to Friday (capping off with the clinical connectathon on Friday), so regardless of what days you're present, there will likely be something of interest.

Participating in the WGM is a good way to get a sense of the people involved in building the spec, to form relationships, to get more deeply involved in the FHIR community and to influence how the standard evolves.

Outcomes (for coordinators)

The following outcomes will be recorded for each track

Results by track

how many completed each track - clients & servers

Key learnings

what changes to the spec resulted from the connectathon?

Changes next time

Does the track need to be repeated next time? (Remember, there are lots to do!) If so, what would be changed?

Overall comments

anything else - what worked, what didn't could the overall organization be changed


Other References

Sub category of FHIR Connectathon Track Proposals for the current connectathon: September 2017 Connectathon 16

Proposals due by : June 7, 2017

Go to prior connectathon proposals: May 2017 Connectathon Proposals

Use this page to submit proposals for tracks for inclusion in the , 2017 connectathon. These proposals will be reviewed and prioritized by the FMG as per the FHIR_Connectathon_Track_Process.

Return to the FHIR Main Page

FHIR Genomics

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