This wiki has undergone a migration to Confluence found Here
Difference between revisions of "2017-03-28 TermInfo Project Call"
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
* 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". | * 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 | + | 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. |
[https://github.com/BD2KOnFHIR/BLENDINGFHIRandRDF Link to tutorial] | [https://github.com/BD2KOnFHIR/BLENDINGFHIRandRDF Link to tutorial] | ||
Revision as of 07:56, 31 March 2017
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
Contunued discussion on document "Using SNOMED CT with HL7 FHIR Resources" - Condtion resource
Update for SNOMED CT concept domain binding based on changes in the last version of FHIR. Representation for intentional value sets. Challenge with implementation of SCT Expression Constraint Language that can be used for describing queries for intentional value set definitions. Useful to know what limitation we have in this work for producing our value sets in FHIR. Example: how to express finding with explicit context but exclude where associated findings are an adminstrative status. Possible requirements for STU 4 to handle this should be identified. Linda provides examples.
