FHIR Agenda-Baltimore 201209 WGM

Saturday

Chesapeake B

• FHIR Connectathon - all day

Sunday

Q1

Anapolis: Joint w/ ARB

Chair/Minutes = ARB

• See FGB topics Friday Q3 below as discussion candidates
• Also FHIR SAIF IG?

Q2

Chesapeake A&B

• Tutorial: Introduction to HL7 FHIR

Q3

Executive Boardroom Joint w/ MnM

Chair/Minutes = MnM

• schedule timeslots & hot topics
• FHIR admin issues (co-chairs, minutes)

Q4

Chesapeake A&B

• Tutorial: Hands on with FHIR
  • Grahame/Ewout, Lloyd second portion

Constellation EF - HL7 Activities with other SDOs

• Lloyd 15-20 minute presentation

Monday

Q3

Convention Center Room 341

• Tutorial: Introduction to HL7 FHIR
  • Only do this if sufficient interest. Alternatively:
• Ballot reconcilliation

Q4

Convention Center Room 341 Host MnM

Chair=Lloyd Minutes=?

• Extensions?
• Mood code Moods in fhir
• Metadata FHIR editing and versions (old)
• FHIR_non-REST_Workflow

Q6

TSC co-chairs presentation

Tuesday

Q0

FHIR Connectathon presentation as part of TSC address - Grahame

Q1

Constellation C - Host ITS, SOA

Chair: ??? Minutes: ???

• ?REST and related issues?
• FHIR Search Parameters
  • What are the conformance expectations?
  • Where should new ones be defined – profile or conformance statement?
  • Should we support sorting? How?

Q2

Constellation C - Host Tooling, V3 pubs

Chair: ??? Minutes: ???

• FHIR tooling & publication issues
  • How to manage publication process, ballot cycle
  • Transition of FHIR tools to Tooling oversight
  • Others?
• FHIR microdata

Q3

Constellation C - Host Patient Administration

Chair: ??? Minutes: ???

• Patient Administration Resource development

Q4

Constellation C - Host InM, ITS

Chair: ??? Minutes: ???

• Message resource

Wednesday

Q1

Constellation C - Host ITS

Chair: ??? Minutes: ???

• XML/JSON/ATOM
• FHIR_Http_Page

Q2

Constellation C - Host Vocabulary

Chair: Lloyd Minutes: ???

• Binding methodology
• [set resource]

Q3

Constellation C - Host OO

Chair: ??? Minutes: ???

• Diagnostic data/reports
• OO-sponsored resources?

Q4

Baltimore - Joint Health Care Devices

Chair: Grahame Minutes: ???

• Device & data registries

Thursday

Q1

Constellation C - Host CGIT, Templates

Chair: ??? Minutes: ???

• Profile resource
• Template registries
• FHIR Conformance Levels Issue Page
• FHIR managing profile identification

Q2

Constellation C - Host Patient Care, Templates

Chair: ??? Minutes: ???

• Care resources
• Use of organizers/summary lists FHIR Workflow resources
• If PC and Templates don't come (as is likely, given they haven't got this listed as joint), we'll do ballot reconcilliation

Q3

Constellation C - Host Structured Documents

Chair: ??? Minutes: ???

• Expressing CDA/SDA in FHIR
  • Document Resources as "header" equivalent
  • selected Document Resource ballot comments (possible)
  • Do we need a "section" resources, or are resources sections?
• Using the FHIR Profile resource for representing CDA templates
• Narrative Status Flag FHIR_Xml_Page#Status Flag
• FHIR general issues (old)#How do we support human readability for resource references?

Q4

Constellation C - SAIF Architecture Program

Chair: ??? Minutes: ???

• FHIR-related SAIF issues

Friday

Q1

Constellation C - Host Pharmacy WG

Chair: ??? Minutes: ???

• Pharmacy resources & extensions

Q2

Constellation C - Host MnM

Chair: ??? Minutes: ???

• Datatypes
• Datatype Profiles FHIR Datatypes Page
• Narrative
• Identifier Type Codes FHIR general issues (old)#Fix identifier type codes

Q3

Constellation C - governance (& management?) groups

Chair: ??? Minutes: ???

• FHIR Principles
• FHIR Governance
• FHIR Business Case Issue Page
• FHIR Project planning
• FHIR Resource Considerations
• Security cookbook (when?) FHIR Security Issues Page
• The Resource With No Name

Q4

Constellation C - governance (& management?) groups

Chair: ??? Minutes: ???

• Agenda Item

Minutes

Mon Q3

• a repeat of the intro to FHIR tutorial

Mon Q4

• ballot reconciliation - recorded in spreadsheet.
• discusion concerning licensing and the preparation process. Recommendation forwarded to the board.
• Discussion concerning extensions, and how they are managed
• Ballot reconciliation for CPP

Tues Q1

• Ballot reconciliation of connectathon issues - see spreadsheet

Tues Q2

• Discussion conerning publishing and tooling
• both publishing and FHIR project happy with current status
• note concerning the need for an HL7 hosted repository - tooling to adopt this as a future requirement

Tues Q3

• presentation from Ewout Kramer concerning PA resource issues
• discussion around related issues:
  • do we have person and patient?
  • what is core?
  • What about related parties?
  • no decisions where made, but comments were added to the wiki
• the project statement was received

Tues Q4

• tutorial concerning messaging in FHIR
• robust discussion about the reliable messaging part
  • decision to allow one of 3 responses on repeat: original response, current response, or error
  • decision to note that message content to be checked, not just id
  • add this to conformance profile
• INM happy for FHIR to continue with the Messaging stuff, would like to be kept informed

Wed Q1

• ballot reconciliation with regard to Json and Xml issues
• decisions recorded in spreadsheet

Wed Q2

• review of vocabulary resources and methodology in FHIR with the vocab committee.
• open issues for FHIR team to work on
  • version - document extension
  • single URLs- work by duplication?
  • URI preference order for identifying code systems? (per Solbrig)
  • Formal...

Wed Q3

• discussion of the general nature of FHIR for O-O
• through review of the LabReport session
• agreement that O-O would work on diagnostic reports
• other things to follow later

Wed Q4

• FHIR met with devices - refer to device minutes
• a general discussion of FHIR, and an agreement to work on a resource for describing Device Capabilities
• possible resources discussed:
• Device (identifies - attribution)
  • carry unit
  • assigned to designated patient
  • photo
• DeviceDescription (describes the capabilities of the device)
  • network interaction capabilities
  • clinical capabilities
• DeviceCommand
  • asks a device to do something
• DeviceCommandResponse
  • report outcome of command
• DeviceReport
  • provide information from a device about clinical world
• device orientated views
  • clinical perspective
  • organisation/asset management
  • Device internal perspective

Thurs Q1

• Discussion about requiring conformance statements - decided to make them required to claim conformance
• decided to allow events to be defined in profiles (same info as in standard, along with reference to IG)
• map events to equivalent HL7 v2 event
• decided to toast the proposal for Conformance levels for now
• brief discussion about the running question of whether to include profile ids in the resource. Comparison to the situation with CDA with which we have considerable experience.
• demonstration of art-decor
  • agreement to consider whether we can express CDA templates in FHIR Profile resource instances. Kai to nominate a few good examples, Grahame to have a go.

Thurs Q2

Problem/Diagnosis - A concern with it's related observations

• Diagnosis : CodeableConcept
• Problem Type (examples:- diagnosis | problem | condition | finding | concern - dig around in snomed / cf with CCDA / ContSys)
• Status x 2 : code?? (CCDA - active, inactive. openEHR - provisional / working / final)
• Onset - Date | Age
• certainty : codeableConcept | %
• DateOfDiagnosis - Date
• resolution / remission - Boolean | Age | Date
• Severity - CodeableConcept
• Clinical Stage/Grade
  • summary - CodeableConcept (0..1)
  • assesssment - Resource(Any) (0..*)
• SupportingEvidence - codeableConcept | Resource(Any) (0..*) (Diagnostic criteria)
• AnatomicalLocation - codeableConcept | Resource(AnatomicalLocation)
• RelatedItem
  • Relationship = causedBy | follows
  • Target - Resource(Problem/Diagnosis|Procedure|Substance)