Basic FHIR Terminology Services AUSTRALIAN E-HEALTH RESEARCH CENTRE, HEALTH & BIOSECURITY Jim Steel, PhD| Senior Software Engineer 16 November 2017 FHIR® is the registered trademark of HL7 and is used with the permission of HL7. The Flame Design mark is the registered trademark of HL7 and is used with the permission of HL7.
43
Embed
Basic FHIR Terminology Services - Home - FHIR DevDays · 2019-03-19 · Terminology: why •Terminology is the basis of shared meaning between different systems •StructureDefinitions
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Basic FHIR Terminology Services
AUSTRALIAN E-HEALTH RESEARCH CENTRE HEALTH amp BIOSECURITY
Jim Steel PhD| Senior Software Engineer16 November 2017
FHIRreg is the registered trademark of HL7 and is used with the permission of HL7 The Flame Design mark is the registered trademark of HL7 and is used with the permission of HL7
Terminology whybull Terminology is the basis of shared meaning between different
systemsbull StructureDefinitions are the bones but terminology defines what goes on
them
bull Terminology (especially ValueSets) is a very important part of defining FHIR profiles
bull Especially in a large integrated system having a single reference for terminology is very valuable for interoperability
bull Externalized terminology makes it much easier to update terminology when it is updatedchanges
Basic Terminology Services | Jim Steel4 |
FHIR Basicsbull SCRUD
bull Search GET ResourcesearchParams or POST Resource_searchbull Create POST Resourcebull Read GET Resourceid (or Resourceid_historyn for VRead)bull Update PUT Resourceidbull Delete DELETE Resourceid
bull Operationsbull GETPOST $operation or Resource$operation or Resourceid$operation
ndash Any parameters go in a lsquoParametersrsquo resource in the request bodybull GET only for idempotent (all can POST)
ndash Can be cached using HTTP cachingbull Servertypeinstance-level depending on the operation
Basic Terminology Services | Jim Steel5 |
CodeSystembull Collection of terms
bull Identified by a URI (and version)
bull Typically in some kind of hierarchy
bull Properties filters
bull Can be infinite
bull Standardised (SNOMED-CT LOINC RxNorm ICD etc) or custom
Basic Terminology Services | Jim Steel6 |
CodeSystem Structure
Basic Terminology Services | Jim Steel7 |
CodeSystem Structure (cont)
Basic Terminology Services | Jim Steel8 |
CodeSystem Structure (cont)
Basic Terminology Services | Jim Steel9 |
CodeSystem example
Basic Terminology Services | Jim Steel10 |
Basic Terminology Services | Jim Steel11 |
CodeSystem example (cont)
Basic Terminology Services | Jim Steel12 |
CodeSystem example (cont)
CodeSystem operations $lookupbull Type level only idempotent (GETPOST CodeSystem$lookup)
bull Retrieve details about a code (as codesystemversion or Coding)
bull Can be used to determine whether a code exists in the CodeSystem
bull Can be used to retrieve specificall propertiesdesignations
Well-known Terminologiesbull Terminologies such as SNOMED-CT LOINC RxNorm have specific
mappings into FHIR terminology resources with standardisedCodeSystemsbull Standard CodeSystem filtersproperties
bull Implicit ValueSets
bull Implicit ConceptMaps
Basic Terminology Services | Jim Steel27 |
Well-known Terminologies SNOMED-CTbull httpsnomedinfosct([edition](version[date]))bull Filters by subsumption by refset by ECL expressionbull Implicit ValueSets
bull All codes httpsnomedinfosctfhir_vs
bull By subsumption httpsnomedinfosctfhir_vs=isa404684003
bull List of refsets httpsnomedinfosctfhir_vs=refset
bull All codes in a refset httpsnomedinfosctfhir_vs=refset734138000
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Terminology whybull Terminology is the basis of shared meaning between different
systemsbull StructureDefinitions are the bones but terminology defines what goes on
them
bull Terminology (especially ValueSets) is a very important part of defining FHIR profiles
bull Especially in a large integrated system having a single reference for terminology is very valuable for interoperability
bull Externalized terminology makes it much easier to update terminology when it is updatedchanges
Basic Terminology Services | Jim Steel4 |
FHIR Basicsbull SCRUD
bull Search GET ResourcesearchParams or POST Resource_searchbull Create POST Resourcebull Read GET Resourceid (or Resourceid_historyn for VRead)bull Update PUT Resourceidbull Delete DELETE Resourceid
bull Operationsbull GETPOST $operation or Resource$operation or Resourceid$operation
ndash Any parameters go in a lsquoParametersrsquo resource in the request bodybull GET only for idempotent (all can POST)
ndash Can be cached using HTTP cachingbull Servertypeinstance-level depending on the operation
Basic Terminology Services | Jim Steel5 |
CodeSystembull Collection of terms
bull Identified by a URI (and version)
bull Typically in some kind of hierarchy
bull Properties filters
bull Can be infinite
bull Standardised (SNOMED-CT LOINC RxNorm ICD etc) or custom
Basic Terminology Services | Jim Steel6 |
CodeSystem Structure
Basic Terminology Services | Jim Steel7 |
CodeSystem Structure (cont)
Basic Terminology Services | Jim Steel8 |
CodeSystem Structure (cont)
Basic Terminology Services | Jim Steel9 |
CodeSystem example
Basic Terminology Services | Jim Steel10 |
Basic Terminology Services | Jim Steel11 |
CodeSystem example (cont)
Basic Terminology Services | Jim Steel12 |
CodeSystem example (cont)
CodeSystem operations $lookupbull Type level only idempotent (GETPOST CodeSystem$lookup)
bull Retrieve details about a code (as codesystemversion or Coding)
bull Can be used to determine whether a code exists in the CodeSystem
bull Can be used to retrieve specificall propertiesdesignations
Well-known Terminologiesbull Terminologies such as SNOMED-CT LOINC RxNorm have specific
mappings into FHIR terminology resources with standardisedCodeSystemsbull Standard CodeSystem filtersproperties
bull Implicit ValueSets
bull Implicit ConceptMaps
Basic Terminology Services | Jim Steel27 |
Well-known Terminologies SNOMED-CTbull httpsnomedinfosct([edition](version[date]))bull Filters by subsumption by refset by ECL expressionbull Implicit ValueSets
bull All codes httpsnomedinfosctfhir_vs
bull By subsumption httpsnomedinfosctfhir_vs=isa404684003
bull List of refsets httpsnomedinfosctfhir_vs=refset
bull All codes in a refset httpsnomedinfosctfhir_vs=refset734138000
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Terminology whybull Terminology is the basis of shared meaning between different
systemsbull StructureDefinitions are the bones but terminology defines what goes on
them
bull Terminology (especially ValueSets) is a very important part of defining FHIR profiles
bull Especially in a large integrated system having a single reference for terminology is very valuable for interoperability
bull Externalized terminology makes it much easier to update terminology when it is updatedchanges
Basic Terminology Services | Jim Steel4 |
FHIR Basicsbull SCRUD
bull Search GET ResourcesearchParams or POST Resource_searchbull Create POST Resourcebull Read GET Resourceid (or Resourceid_historyn for VRead)bull Update PUT Resourceidbull Delete DELETE Resourceid
bull Operationsbull GETPOST $operation or Resource$operation or Resourceid$operation
ndash Any parameters go in a lsquoParametersrsquo resource in the request bodybull GET only for idempotent (all can POST)
ndash Can be cached using HTTP cachingbull Servertypeinstance-level depending on the operation
Basic Terminology Services | Jim Steel5 |
CodeSystembull Collection of terms
bull Identified by a URI (and version)
bull Typically in some kind of hierarchy
bull Properties filters
bull Can be infinite
bull Standardised (SNOMED-CT LOINC RxNorm ICD etc) or custom
Basic Terminology Services | Jim Steel6 |
CodeSystem Structure
Basic Terminology Services | Jim Steel7 |
CodeSystem Structure (cont)
Basic Terminology Services | Jim Steel8 |
CodeSystem Structure (cont)
Basic Terminology Services | Jim Steel9 |
CodeSystem example
Basic Terminology Services | Jim Steel10 |
Basic Terminology Services | Jim Steel11 |
CodeSystem example (cont)
Basic Terminology Services | Jim Steel12 |
CodeSystem example (cont)
CodeSystem operations $lookupbull Type level only idempotent (GETPOST CodeSystem$lookup)
bull Retrieve details about a code (as codesystemversion or Coding)
bull Can be used to determine whether a code exists in the CodeSystem
bull Can be used to retrieve specificall propertiesdesignations
Well-known Terminologiesbull Terminologies such as SNOMED-CT LOINC RxNorm have specific
mappings into FHIR terminology resources with standardisedCodeSystemsbull Standard CodeSystem filtersproperties
bull Implicit ValueSets
bull Implicit ConceptMaps
Basic Terminology Services | Jim Steel27 |
Well-known Terminologies SNOMED-CTbull httpsnomedinfosct([edition](version[date]))bull Filters by subsumption by refset by ECL expressionbull Implicit ValueSets
bull All codes httpsnomedinfosctfhir_vs
bull By subsumption httpsnomedinfosctfhir_vs=isa404684003
bull List of refsets httpsnomedinfosctfhir_vs=refset
bull All codes in a refset httpsnomedinfosctfhir_vs=refset734138000
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
bull Search GET ResourcesearchParams or POST Resource_searchbull Create POST Resourcebull Read GET Resourceid (or Resourceid_historyn for VRead)bull Update PUT Resourceidbull Delete DELETE Resourceid
bull Operationsbull GETPOST $operation or Resource$operation or Resourceid$operation
ndash Any parameters go in a lsquoParametersrsquo resource in the request bodybull GET only for idempotent (all can POST)
ndash Can be cached using HTTP cachingbull Servertypeinstance-level depending on the operation
Basic Terminology Services | Jim Steel5 |
CodeSystembull Collection of terms
bull Identified by a URI (and version)
bull Typically in some kind of hierarchy
bull Properties filters
bull Can be infinite
bull Standardised (SNOMED-CT LOINC RxNorm ICD etc) or custom
Basic Terminology Services | Jim Steel6 |
CodeSystem Structure
Basic Terminology Services | Jim Steel7 |
CodeSystem Structure (cont)
Basic Terminology Services | Jim Steel8 |
CodeSystem Structure (cont)
Basic Terminology Services | Jim Steel9 |
CodeSystem example
Basic Terminology Services | Jim Steel10 |
Basic Terminology Services | Jim Steel11 |
CodeSystem example (cont)
Basic Terminology Services | Jim Steel12 |
CodeSystem example (cont)
CodeSystem operations $lookupbull Type level only idempotent (GETPOST CodeSystem$lookup)
bull Retrieve details about a code (as codesystemversion or Coding)
bull Can be used to determine whether a code exists in the CodeSystem
bull Can be used to retrieve specificall propertiesdesignations
Well-known Terminologiesbull Terminologies such as SNOMED-CT LOINC RxNorm have specific
mappings into FHIR terminology resources with standardisedCodeSystemsbull Standard CodeSystem filtersproperties
bull Implicit ValueSets
bull Implicit ConceptMaps
Basic Terminology Services | Jim Steel27 |
Well-known Terminologies SNOMED-CTbull httpsnomedinfosct([edition](version[date]))bull Filters by subsumption by refset by ECL expressionbull Implicit ValueSets
bull All codes httpsnomedinfosctfhir_vs
bull By subsumption httpsnomedinfosctfhir_vs=isa404684003
bull List of refsets httpsnomedinfosctfhir_vs=refset
bull All codes in a refset httpsnomedinfosctfhir_vs=refset734138000
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Well-known Terminologiesbull Terminologies such as SNOMED-CT LOINC RxNorm have specific
mappings into FHIR terminology resources with standardisedCodeSystemsbull Standard CodeSystem filtersproperties
bull Implicit ValueSets
bull Implicit ConceptMaps
Basic Terminology Services | Jim Steel27 |
Well-known Terminologies SNOMED-CTbull httpsnomedinfosct([edition](version[date]))bull Filters by subsumption by refset by ECL expressionbull Implicit ValueSets
bull All codes httpsnomedinfosctfhir_vs
bull By subsumption httpsnomedinfosctfhir_vs=isa404684003
bull List of refsets httpsnomedinfosctfhir_vs=refset
bull All codes in a refset httpsnomedinfosctfhir_vs=refset734138000
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Well-known Terminologiesbull Terminologies such as SNOMED-CT LOINC RxNorm have specific
mappings into FHIR terminology resources with standardisedCodeSystemsbull Standard CodeSystem filtersproperties
bull Implicit ValueSets
bull Implicit ConceptMaps
Basic Terminology Services | Jim Steel27 |
Well-known Terminologies SNOMED-CTbull httpsnomedinfosct([edition](version[date]))bull Filters by subsumption by refset by ECL expressionbull Implicit ValueSets
bull All codes httpsnomedinfosctfhir_vs
bull By subsumption httpsnomedinfosctfhir_vs=isa404684003
bull List of refsets httpsnomedinfosctfhir_vs=refset
bull All codes in a refset httpsnomedinfosctfhir_vs=refset734138000
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Well-known Terminologiesbull Terminologies such as SNOMED-CT LOINC RxNorm have specific
mappings into FHIR terminology resources with standardisedCodeSystemsbull Standard CodeSystem filtersproperties
bull Implicit ValueSets
bull Implicit ConceptMaps
Basic Terminology Services | Jim Steel27 |
Well-known Terminologies SNOMED-CTbull httpsnomedinfosct([edition](version[date]))bull Filters by subsumption by refset by ECL expressionbull Implicit ValueSets
bull All codes httpsnomedinfosctfhir_vs
bull By subsumption httpsnomedinfosctfhir_vs=isa404684003
bull List of refsets httpsnomedinfosctfhir_vs=refset
bull All codes in a refset httpsnomedinfosctfhir_vs=refset734138000
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Well-known Terminologiesbull Terminologies such as SNOMED-CT LOINC RxNorm have specific
mappings into FHIR terminology resources with standardisedCodeSystemsbull Standard CodeSystem filtersproperties
bull Implicit ValueSets
bull Implicit ConceptMaps
Basic Terminology Services | Jim Steel27 |
Well-known Terminologies SNOMED-CTbull httpsnomedinfosct([edition](version[date]))bull Filters by subsumption by refset by ECL expressionbull Implicit ValueSets
bull All codes httpsnomedinfosctfhir_vs
bull By subsumption httpsnomedinfosctfhir_vs=isa404684003
bull List of refsets httpsnomedinfosctfhir_vs=refset
bull All codes in a refset httpsnomedinfosctfhir_vs=refset734138000
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Well-known Terminologiesbull Terminologies such as SNOMED-CT LOINC RxNorm have specific
mappings into FHIR terminology resources with standardisedCodeSystemsbull Standard CodeSystem filtersproperties
bull Implicit ValueSets
bull Implicit ConceptMaps
Basic Terminology Services | Jim Steel27 |
Well-known Terminologies SNOMED-CTbull httpsnomedinfosct([edition](version[date]))bull Filters by subsumption by refset by ECL expressionbull Implicit ValueSets
bull All codes httpsnomedinfosctfhir_vs
bull By subsumption httpsnomedinfosctfhir_vs=isa404684003
bull List of refsets httpsnomedinfosctfhir_vs=refset
bull All codes in a refset httpsnomedinfosctfhir_vs=refset734138000
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Well-known Terminologiesbull Terminologies such as SNOMED-CT LOINC RxNorm have specific
mappings into FHIR terminology resources with standardisedCodeSystemsbull Standard CodeSystem filtersproperties
bull Implicit ValueSets
bull Implicit ConceptMaps
Basic Terminology Services | Jim Steel27 |
Well-known Terminologies SNOMED-CTbull httpsnomedinfosct([edition](version[date]))bull Filters by subsumption by refset by ECL expressionbull Implicit ValueSets
bull All codes httpsnomedinfosctfhir_vs
bull By subsumption httpsnomedinfosctfhir_vs=isa404684003
bull List of refsets httpsnomedinfosctfhir_vs=refset
bull All codes in a refset httpsnomedinfosctfhir_vs=refset734138000
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Well-known Terminologiesbull Terminologies such as SNOMED-CT LOINC RxNorm have specific
mappings into FHIR terminology resources with standardisedCodeSystemsbull Standard CodeSystem filtersproperties
bull Implicit ValueSets
bull Implicit ConceptMaps
Basic Terminology Services | Jim Steel27 |
Well-known Terminologies SNOMED-CTbull httpsnomedinfosct([edition](version[date]))bull Filters by subsumption by refset by ECL expressionbull Implicit ValueSets
bull All codes httpsnomedinfosctfhir_vs
bull By subsumption httpsnomedinfosctfhir_vs=isa404684003
bull List of refsets httpsnomedinfosctfhir_vs=refset
bull All codes in a refset httpsnomedinfosctfhir_vs=refset734138000
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Well-known Terminologiesbull Terminologies such as SNOMED-CT LOINC RxNorm have specific
mappings into FHIR terminology resources with standardisedCodeSystemsbull Standard CodeSystem filtersproperties
bull Implicit ValueSets
bull Implicit ConceptMaps
Basic Terminology Services | Jim Steel27 |
Well-known Terminologies SNOMED-CTbull httpsnomedinfosct([edition](version[date]))bull Filters by subsumption by refset by ECL expressionbull Implicit ValueSets
bull All codes httpsnomedinfosctfhir_vs
bull By subsumption httpsnomedinfosctfhir_vs=isa404684003
bull List of refsets httpsnomedinfosctfhir_vs=refset
bull All codes in a refset httpsnomedinfosctfhir_vs=refset734138000
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Well-known Terminologiesbull Terminologies such as SNOMED-CT LOINC RxNorm have specific
mappings into FHIR terminology resources with standardisedCodeSystemsbull Standard CodeSystem filtersproperties
bull Implicit ValueSets
bull Implicit ConceptMaps
Basic Terminology Services | Jim Steel27 |
Well-known Terminologies SNOMED-CTbull httpsnomedinfosct([edition](version[date]))bull Filters by subsumption by refset by ECL expressionbull Implicit ValueSets
bull All codes httpsnomedinfosctfhir_vs
bull By subsumption httpsnomedinfosctfhir_vs=isa404684003
bull List of refsets httpsnomedinfosctfhir_vs=refset
bull All codes in a refset httpsnomedinfosctfhir_vs=refset734138000
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Well-known Terminologiesbull Terminologies such as SNOMED-CT LOINC RxNorm have specific
mappings into FHIR terminology resources with standardisedCodeSystemsbull Standard CodeSystem filtersproperties
bull Implicit ValueSets
bull Implicit ConceptMaps
Basic Terminology Services | Jim Steel27 |
Well-known Terminologies SNOMED-CTbull httpsnomedinfosct([edition](version[date]))bull Filters by subsumption by refset by ECL expressionbull Implicit ValueSets
bull All codes httpsnomedinfosctfhir_vs
bull By subsumption httpsnomedinfosctfhir_vs=isa404684003
bull List of refsets httpsnomedinfosctfhir_vs=refset
bull All codes in a refset httpsnomedinfosctfhir_vs=refset734138000
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Well-known Terminologiesbull Terminologies such as SNOMED-CT LOINC RxNorm have specific
mappings into FHIR terminology resources with standardisedCodeSystemsbull Standard CodeSystem filtersproperties
bull Implicit ValueSets
bull Implicit ConceptMaps
Basic Terminology Services | Jim Steel27 |
Well-known Terminologies SNOMED-CTbull httpsnomedinfosct([edition](version[date]))bull Filters by subsumption by refset by ECL expressionbull Implicit ValueSets
bull All codes httpsnomedinfosctfhir_vs
bull By subsumption httpsnomedinfosctfhir_vs=isa404684003
bull List of refsets httpsnomedinfosctfhir_vs=refset
bull All codes in a refset httpsnomedinfosctfhir_vs=refset734138000
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Well-known Terminologiesbull Terminologies such as SNOMED-CT LOINC RxNorm have specific
mappings into FHIR terminology resources with standardisedCodeSystemsbull Standard CodeSystem filtersproperties
bull Implicit ValueSets
bull Implicit ConceptMaps
Basic Terminology Services | Jim Steel27 |
Well-known Terminologies SNOMED-CTbull httpsnomedinfosct([edition](version[date]))bull Filters by subsumption by refset by ECL expressionbull Implicit ValueSets
bull All codes httpsnomedinfosctfhir_vs
bull By subsumption httpsnomedinfosctfhir_vs=isa404684003
bull List of refsets httpsnomedinfosctfhir_vs=refset
bull All codes in a refset httpsnomedinfosctfhir_vs=refset734138000
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Well-known Terminologiesbull Terminologies such as SNOMED-CT LOINC RxNorm have specific
mappings into FHIR terminology resources with standardisedCodeSystemsbull Standard CodeSystem filtersproperties
bull Implicit ValueSets
bull Implicit ConceptMaps
Basic Terminology Services | Jim Steel27 |
Well-known Terminologies SNOMED-CTbull httpsnomedinfosct([edition](version[date]))bull Filters by subsumption by refset by ECL expressionbull Implicit ValueSets
bull All codes httpsnomedinfosctfhir_vs
bull By subsumption httpsnomedinfosctfhir_vs=isa404684003
bull List of refsets httpsnomedinfosctfhir_vs=refset
bull All codes in a refset httpsnomedinfosctfhir_vs=refset734138000
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Well-known Terminologiesbull Terminologies such as SNOMED-CT LOINC RxNorm have specific
mappings into FHIR terminology resources with standardisedCodeSystemsbull Standard CodeSystem filtersproperties
bull Implicit ValueSets
bull Implicit ConceptMaps
Basic Terminology Services | Jim Steel27 |
Well-known Terminologies SNOMED-CTbull httpsnomedinfosct([edition](version[date]))bull Filters by subsumption by refset by ECL expressionbull Implicit ValueSets
bull All codes httpsnomedinfosctfhir_vs
bull By subsumption httpsnomedinfosctfhir_vs=isa404684003
bull List of refsets httpsnomedinfosctfhir_vs=refset
bull All codes in a refset httpsnomedinfosctfhir_vs=refset734138000
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Well-known Terminologiesbull Terminologies such as SNOMED-CT LOINC RxNorm have specific
mappings into FHIR terminology resources with standardisedCodeSystemsbull Standard CodeSystem filtersproperties
bull Implicit ValueSets
bull Implicit ConceptMaps
Basic Terminology Services | Jim Steel27 |
Well-known Terminologies SNOMED-CTbull httpsnomedinfosct([edition](version[date]))bull Filters by subsumption by refset by ECL expressionbull Implicit ValueSets
bull All codes httpsnomedinfosctfhir_vs
bull By subsumption httpsnomedinfosctfhir_vs=isa404684003
bull List of refsets httpsnomedinfosctfhir_vs=refset
bull All codes in a refset httpsnomedinfosctfhir_vs=refset734138000
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Well-known Terminologiesbull Terminologies such as SNOMED-CT LOINC RxNorm have specific
mappings into FHIR terminology resources with standardisedCodeSystemsbull Standard CodeSystem filtersproperties
bull Implicit ValueSets
bull Implicit ConceptMaps
Basic Terminology Services | Jim Steel27 |
Well-known Terminologies SNOMED-CTbull httpsnomedinfosct([edition](version[date]))bull Filters by subsumption by refset by ECL expressionbull Implicit ValueSets
bull All codes httpsnomedinfosctfhir_vs
bull By subsumption httpsnomedinfosctfhir_vs=isa404684003
bull List of refsets httpsnomedinfosctfhir_vs=refset
bull All codes in a refset httpsnomedinfosctfhir_vs=refset734138000
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Well-known Terminologiesbull Terminologies such as SNOMED-CT LOINC RxNorm have specific
mappings into FHIR terminology resources with standardisedCodeSystemsbull Standard CodeSystem filtersproperties
bull Implicit ValueSets
bull Implicit ConceptMaps
Basic Terminology Services | Jim Steel27 |
Well-known Terminologies SNOMED-CTbull httpsnomedinfosct([edition](version[date]))bull Filters by subsumption by refset by ECL expressionbull Implicit ValueSets
bull All codes httpsnomedinfosctfhir_vs
bull By subsumption httpsnomedinfosctfhir_vs=isa404684003
bull List of refsets httpsnomedinfosctfhir_vs=refset
bull All codes in a refset httpsnomedinfosctfhir_vs=refset734138000
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Well-known Terminologiesbull Terminologies such as SNOMED-CT LOINC RxNorm have specific
mappings into FHIR terminology resources with standardisedCodeSystemsbull Standard CodeSystem filtersproperties
bull Implicit ValueSets
bull Implicit ConceptMaps
Basic Terminology Services | Jim Steel27 |
Well-known Terminologies SNOMED-CTbull httpsnomedinfosct([edition](version[date]))bull Filters by subsumption by refset by ECL expressionbull Implicit ValueSets
bull All codes httpsnomedinfosctfhir_vs
bull By subsumption httpsnomedinfosctfhir_vs=isa404684003
bull List of refsets httpsnomedinfosctfhir_vs=refset
bull All codes in a refset httpsnomedinfosctfhir_vs=refset734138000
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Well-known Terminologiesbull Terminologies such as SNOMED-CT LOINC RxNorm have specific
mappings into FHIR terminology resources with standardisedCodeSystemsbull Standard CodeSystem filtersproperties
bull Implicit ValueSets
bull Implicit ConceptMaps
Basic Terminology Services | Jim Steel27 |
Well-known Terminologies SNOMED-CTbull httpsnomedinfosct([edition](version[date]))bull Filters by subsumption by refset by ECL expressionbull Implicit ValueSets
bull All codes httpsnomedinfosctfhir_vs
bull By subsumption httpsnomedinfosctfhir_vs=isa404684003
bull List of refsets httpsnomedinfosctfhir_vs=refset
bull All codes in a refset httpsnomedinfosctfhir_vs=refset734138000
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Well-known Terminologiesbull Terminologies such as SNOMED-CT LOINC RxNorm have specific
mappings into FHIR terminology resources with standardisedCodeSystemsbull Standard CodeSystem filtersproperties
bull Implicit ValueSets
bull Implicit ConceptMaps
Basic Terminology Services | Jim Steel27 |
Well-known Terminologies SNOMED-CTbull httpsnomedinfosct([edition](version[date]))bull Filters by subsumption by refset by ECL expressionbull Implicit ValueSets
bull All codes httpsnomedinfosctfhir_vs
bull By subsumption httpsnomedinfosctfhir_vs=isa404684003
bull List of refsets httpsnomedinfosctfhir_vs=refset
bull All codes in a refset httpsnomedinfosctfhir_vs=refset734138000
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Well-known Terminologiesbull Terminologies such as SNOMED-CT LOINC RxNorm have specific
mappings into FHIR terminology resources with standardisedCodeSystemsbull Standard CodeSystem filtersproperties
bull Implicit ValueSets
bull Implicit ConceptMaps
Basic Terminology Services | Jim Steel27 |
Well-known Terminologies SNOMED-CTbull httpsnomedinfosct([edition](version[date]))bull Filters by subsumption by refset by ECL expressionbull Implicit ValueSets
bull All codes httpsnomedinfosctfhir_vs
bull By subsumption httpsnomedinfosctfhir_vs=isa404684003
bull List of refsets httpsnomedinfosctfhir_vs=refset
bull All codes in a refset httpsnomedinfosctfhir_vs=refset734138000
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Well-known Terminologiesbull Terminologies such as SNOMED-CT LOINC RxNorm have specific
mappings into FHIR terminology resources with standardisedCodeSystemsbull Standard CodeSystem filtersproperties
bull Implicit ValueSets
bull Implicit ConceptMaps
Basic Terminology Services | Jim Steel27 |
Well-known Terminologies SNOMED-CTbull httpsnomedinfosct([edition](version[date]))bull Filters by subsumption by refset by ECL expressionbull Implicit ValueSets
bull All codes httpsnomedinfosctfhir_vs
bull By subsumption httpsnomedinfosctfhir_vs=isa404684003
bull List of refsets httpsnomedinfosctfhir_vs=refset
bull All codes in a refset httpsnomedinfosctfhir_vs=refset734138000
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Well-known Terminologies SNOMED-CTbull httpsnomedinfosct([edition](version[date]))bull Filters by subsumption by refset by ECL expressionbull Implicit ValueSets
bull All codes httpsnomedinfosctfhir_vs
bull By subsumption httpsnomedinfosctfhir_vs=isa404684003
bull List of refsets httpsnomedinfosctfhir_vs=refset
bull All codes in a refset httpsnomedinfosctfhir_vs=refset734138000
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
Conditions where the finding site is a descendent of Bone Structure
bull innot-inbull Eg
ProcedureRequestcodein=httpsnomedinfosctfhir_vs=refset32570361000036108 (all ProcedureRequests in the Imagine Procedure refset
Basic Terminology Services | Jim Steel37 |
Tips and tricksbull Paging
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
bull Search results can be paged (httphl7orgfhirsearchhtml see _count parameter)
bull $expand results have a separate paging mechanism (count offset)
bull Can reduce bandwidthresponse times by requesting the specific elements you wantbull includeDefinition includeDesignations on $expand
bull property on $lookup
bull _elements on searchreadoperation results
Basic Terminology Services | Jim Steel38 |
Tips and Tricks (cont)bull Batch
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
bull A lot of terminology operations are small ndash it can often be more efficient to send them as a batch (httphl7orgfhirhttphtmltransaction) then deal with the result when it comes back
bull Manage content types (Content-Type Accept _format)bull JSON XML
bull Accept-Encoding gzipbull More tips in the advanced session
Warning A lot of these can be server-dependent Theyrsquore not proprietary but you should check support for them by your terminology server
Basic Terminology Services | Jim Steel39 |
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
What if I am hellipbull Designing interfaces for data entry
bull Choose your CodeSystems (ideally standardized ones)
bull Choose or define your ValueSets
bull If your ValueSet is small a picklist can be populated using $expand
bull If your ValueSet is large a typeahead widget can use $expandfilter=xxx
Basic Terminology Services | Jim Steel40 |
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
bull Making a profilebull Choosedefine which code systems you want to allow
bull Make ValueSets with lists of codes you want to allow
ndash Make sure you respect the binding strength
bull Set up some processes for maintainingupdating them
ndash Concepts can become deprecated over time you can sometimes use ConceptMaps to find which concepts have changed
Basic Terminology Services | Jim Steel41 |
What if I amhellip
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts
What if I am hellipbull Analyzingvalidating coded data
bull Choose your CodeSystemValueSets
bull Use $validate-code to check whether the codes are valid in the context in which yoursquore using them and whether the display text is correct (many clinical systems allow users to override the display text for the term)
bull Use $translate to map lsquoforeignrsquo coded data into a normalized CodeSystemValueSet for analysis
bull Use $subsumes $closure or $validate-code with an inline ValueSet to categorize data
Basic Terminology Services | Jim Steel42 |
What if I am hellipbull Exploring a set of concepts and how they relate to one another
bull Use $lookup to retrieve their properties and display them in a table
bull Use the lsquochildrsquo and lsquoparentrsquo properties or $subsumes$closure to explore the hierarchy that exists between concepts