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

Difference between revisions of "2017-04-04 TermInfo Project Call"

From HL7Wiki
Jump to navigation Jump to search
Line 133: Line 133:
 
     [https://github.com/BD2KOnFHIR/BLENDINGFHIRandRDF Link to tutorial]
 
     [https://github.com/BD2KOnFHIR/BLENDINGFHIRandRDF Link to tutorial]
  
 +
'''Discussion on deliveries'''
 +
* Agreement that main deliveries are FHIR profiles for SNOMED. Suggestion that we start next meeting preparing for starting work directly on output to the extent possible.
  
−
'''Contunued discussion on document "Using SNOMED CT with HL7 FHIR Resources" - Condtion resource'''  
+
'''Discussion on SNOMED CT-binding'''
−
* Condition resource/ manifestation or symptom. Is not fully compatible with the SCT concept model. Value set is all of descendents of Clinical Finding – should remove some subhierachies.  
+
Discussion on prepared material from Linda on clinical status. What are the semantic dependencies and combined meaning of the attributes Clinical Status and Verification Status. And how does this translate consistently to SNOMED CT. Possible representation candidates are Known, Known possible, Known absent (qualifier values). Lack of specific definition of attributes in FHIR.  
−
* Body site value – expansion of anatomical structure. Should cell structure be included? In almost all use cases that would not be relevant. Body structure can be precoordinated into the condition itself > semantic overlap. > use of RDF for crossover.  
 
  
−
''HL7 value sets in the Condition resource that should be considered converted to SCT:''  
+
'''Meeting duration'''
−
*Condition category. Definition of category. Clinical finding or disorder or findings? Ex preganancy? This field is not useful unless it restricts the Category across the board in FHIR – simple set of category values to do something with the data (without even understanding the code itself) you can still figure out what to do with the data – bucket. They are however treated in different ways. This one is CodeableConcept.
+
We will try out 90 min calls from next week.
−
*Problem-list-item/ encounter diagnosis
 
−
*Clincal status and verification status  also not using SNOMED CT.
 
−
 
 
−
How can we maintain terminology binding over time? SCT term amended to FHIR – how to make this formal and maintainable. Terminfo artefact? 
 
−
 
 
−
 
 
−
Should we extend the call 90 min?
 

Revision as of 11:08, 7 April 2017

Meeting Information

TermInfo Project Conference Call

GTM and call-in details:

1. Please join my meeting. https://global.gotomeeting.com/meeting/join/605884653

2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone.

Australia: +61 2 8355 1040 Canada: +1 (647) 497-9391 Denmark: +45 (0) 69 91 88 61 Sweden: +46 (0) 852 503 498 United Kingdom: +44 20 3535 0624 United States: +1 (646) 982-0002

Date: 2016-03-28
Time: 4:00-5:00pm ET
Chair Rob Hausam Scribe Øyvind Aassve
Attendee Name Affiliation


Rob Hausam Hausam Consulting LLC
Linda Bird SNOMED International
Carmela Couderc SNOMED International
Peter Jordan HL7 New Zealand
Øyvind Aassve Norwegian Directorate of e-health
Quorum Requirements Met: yes

Agenda

Agenda Topics

  • Announcements
  • Minutes (as available. Review minutes on Wiki - thanks, Oyvind!
  • Review action items (send any updates in advance!)
    • Invite Harold Solbrig to discuss and provide a further demo of the SNOMED CT/FHIR reasoning using OWL/Protege
    • Review and update TermInfo PSS
  • Update TermInfo Wiki and HL7 TermInfo project site information
  • Call duration. Continue with 60 minutes or extend to 90?
  • Continue FHIR SNOMED CT Model Meaning Binding and Value Set Review
  • The "Using SNOMED CT with HL7 FHIR Resources" document was distributed on Feb. 13
  • Further review or answer questions regarding FHIR IG publishing process and tools (if time permitting)

Minutes

Initial discussion/review of reasoning across FHIR and SNOMED CT using OWL

  • Rob presented "Tutorial" on blending FHIR and RDF in Protégé. Work from RDF group by Harold Solbrig. Mechanisms for crossing the information model and terminology. Agreement this is very interesting, and an approach that could facilitate "computable TermInfo".

Questions: How have FHIR resources been bound to the SCT condept model? The translation from creating OWL from SNOMED is not based on IHTSDOs Pearl-script. 

   Link to tutorial

Discussion on deliveries

  • Agreement that main deliveries are FHIR profiles for SNOMED. Suggestion that we start next meeting preparing for starting work directly on output to the extent possible.

Discussion on SNOMED CT-binding Discussion on prepared material from Linda on clinical status. What are the semantic dependencies and combined meaning of the attributes Clinical Status and Verification Status. And how does this translate consistently to SNOMED CT. Possible representation candidates are Known, Known possible, Known absent (qualifier values). Lack of specific definition of attributes in FHIR.

Meeting duration We will try out 90 min calls from next week.

Retrieved from "https://wiki.hl7.org/w/index.php?title=2017-04-04_TermInfo_Project_Call&oldid=137311"