FHIR Chat · Terminology Services Track · connectathon mgmt

Stream: connectathon mgmt

Topic: Terminology Services Track

Grahame Grieve (Dec 23 2017 at 22:42):

@Rob Hausam there's been a bunch of discussion about the track on the terminology stream. Are we going to extend the scenarios?

Rob Hausam (Dec 24 2017 at 16:27):

Yes. I'll be spending time on that and other items for New Orleans over the next few days between the holidays.

Peter Jordan (Dec 24 2017 at 20:22):

@Rob Hausam I'll be on deck until Dec 31, so happy to help (e.g. updating links to the spec on the Wiki Page, etc.).

Rob Hausam (Dec 25 2017 at 03:26):

@Peter Jordan Thanks. And merry Christmas!

Peter Jordan (Dec 27 2017 at 22:45):

Updated all the links to the spec on the Wiki Page and added a couple for new operations (CodeSystem/$validate-code) and the TS Capability Statement. Also modified some links to test servers and other resources (e.g. this stream). Will need to amend the Test Script references once the C17 ones have been added to Touchstone.

Peter Jordan (Jan 08 2018 at 23:49):

@Richard Ettema & @Rob Hausam, any thoughts on the following properties for the terminology test artifacts - id, url, identifier, name, title and version? At a minimum, maybe we should make the ('computer-friendly') names and versions reflect the Connectathon Number (17)?

Richard Ettema (Jan 09 2018 at 21:47):

@Peter Jordan I plan to start working on the Connecathon 17 TestScripts some time tomorrow. My first task will be to copy forward the Connectathon 16 TestScripts and update them based on any FHIR R4 (v3.2.0) changes. Once that is done, I can start to examine the resource fixture elements.

Peter Jordan (Jan 09 2018 at 22:51):

Excellent @Richard Ettema. I don't think that there are any R4 changes that will break those scripts. @Rob Hausam has suggested that we meet on-line (this week?) to discuss the fixture elements and additional tests.

Something we should definitely add are tests for the new CodeSystem $validate-code operation. Should be relatively easy to clone and adapt these from the ValueSet $validate-code tests.

Grahame Grieve (Jan 09 2018 at 23:13):

supplements should get tested

Peter Jordan (Jan 09 2018 at 23:54):

Do you have an example of a Code System resource with supplements that we might use? I was going to cobble something together using an NZ test resource, mainly to test FHIR versioning, but I'm hoping that you might have something better that everyone might use (e.g. an HL7 Code System).

Grahame Grieve (Jan 10 2018 at 00:17):

{
    "resourceType": "CodeSystem",
    "id": "1",
    "meta": {
        "versionId": "2",
        "lastUpdated": "2017-12-28T06:53:07Z"
    },
    "language": "de",
    "url": "http://hl7.org/fhir/bundle-type-de",
    "version": "3.2.0",
    "name": "BundleTypeGerman",
    "status": "draft",
    "experimental": false,
    "date": "2017-12-21T16:40:38+11:00",
    "publisher": "HL7 (FHIR Project)",
    "description": "German Translations for Bundle Type",
    "content": "supplement",
    "supplements": {
        "reference": "http://hl7.org/fhir/bundle-type"
    },
    "concept": [
        {
            "code": "document",
            "display": "Dokument"
        },
        {
            "code": "message",
            "display": "Nachricht"
        },
        {
            "code": "transaction",
            "display": "Transaktion"
        },
        {
            "code": "transaction-response",
            "display": "Transaktionsantwort"
        },
        {
            "code": "batch",
            "display": "Stapel"
        },
        {
            "code": "batch-response",
            "display": "Batch-Antwort"
        },
        {
            "code": "history",
            "display": "Verlaufsliste"
        },
        {
            "code": "searchset",
            "display": "Suchergebnisse"
        },
        {
            "code": "collection",
            "display": "Sammlung"
        }
    ]
}

Rob Hausam (Jan 10 2018 at 13:20):

@Richard Ettema That's great. Yes, let's find a time to get togther on this. We need to take advantage to the extent that we can of the connectathon tooling and the additional time that we will have available with the full day on Sunday.

Rob Hausam (Jan 10 2018 at 13:28):

@Grahame Grieve Thanks for the supplement example. That's at least a start. Maybe we can come up with one for a SNOMED CT subset, too - the Canadian or one of the European NRC's might have something that they could share?

Richard Ettema (Jan 10 2018 at 16:25):

@Peter Jordan & @Rob Hausam We're [AEGIS] working on getting Touchstone updated with support for FHIR R4 (v3.2.0) by COB tomorrow. I should have the Terminology tests (as-is) available very soon after that. My schedule for the next couple of days is pretty open for a meeting.

Rob Hausam (Jan 10 2018 at 23:15):

That's great. I just mentioned to Sandy that I would be asking you about the plans for Touchstone in regard to the FHIR versions.

Grahame Grieve (Jan 11 2018 at 04:10):

Supplement for Snomed - what would it say?

Yunwei Wang (Jan 19 2018 at 16:04):

@Rob Hausam Can you send me the orientation PPT?

Rob Hausam (Jan 20 2018 at 00:18):

Done.

Rob Hausam (Jan 27 2018 at 15:33):

We are meeting for a TS track breakout session now in the Royal room. If you are participating in the track come and join us.

Rob Hausam (Jan 27 2018 at 16:38):

Make sure that you register in the Connectathon Management Tool at http://snapp.clinfhir.com:4000/ - register yourself, clients and servers, and then set up the testing (and other track activities) and record the test results. Thanks!

Rob Hausam (Jan 27 2018 at 16:39):

If you are needing a copy of the orientation slides, let me know.

Michael Calderero (Jan 27 2018 at 21:42):

Hi Guys,

I got a question on a certain part of the terminology specification. Not sure if I post it here or there's a separate stream for discussing terminology-related questions?

Grahame Grieve (Jan 27 2018 at 21:43):

https://chat.fhir.org/#narrow/stream/terminology

Rob Hausam (Jan 28 2018 at 15:28):

David Hay is adding a new scenario in our track for general comments. By the end of the day (the sooner the better) I would like for all of us to use the tool to report on our activities over the two days. Let me know if it doesn't seem to be clear how to do it or it isn't working. What David is saying and showing right now should help.

David Hay (Jan 28 2018 at 15:53):

Should be in there now...

Rob Hausam (Jan 28 2018 at 20:00):

Yes, thanks, David. It's available for everyone to use now for recording your track activities.

Peter Jordan (Jan 28 2018 at 20:48):

@David Hay. Looks like a bug/problem with CM Tool - keep losing entries in results tab!...

Update - fixed by re-added Test Server to all scenarios.

Rob Hausam (May 13 2018 at 07:04):

Good morning, everyone. It's already the second day of the Connectathon, and I'm thinking about our report at the end. If you could all send me a brief note about what you've been doing and what you've been able to accomplish, or any issues that you've encountered or suggestions that you have, that would be great. And if you can do that sometime this morning (and update it later in the day, if needed), that would be really great. Thanks!

Carol Macumber (May 13 2018 at 08:16):

Hi Rob - here's what we've done this morning - Collaborated with the Clinical Reasoning track to support expansion of of NCQA Cervical Cancer screening value sets for the Storage and Analytics track

Peter Jordan (May 13 2018 at 09:18):

I've recorded all the Touchstone testing of my server (Terminz) in ConMan. Also worthy of note is the tutorials on creating Test Scripts - I've managed to create a new script (to test request expansions of a couple of the test Value Sets using the valueSetVersion parameter) which has been successfully loaded to, and executed from, Touchstone.

Stefan Karl (May 13 2018 at 10:02):

I created a sample CodeSystem resource for the 11073MDC terminology system using XSL transformation from the Rosetta database contents. Also trying out value set expansion based on property filters.

Grahame Grieve (May 13 2018 at 11:30):

where is it?

Stefan Karl (May 13 2018 at 12:57):

http://hapi.fhir.org/baseDstu3/CodeSystem?url=urn:iso:std:iso:11073:10101

Grahame Grieve (May 13 2018 at 13:35):

thx

Joel Schneider (May 14 2018 at 08:23):

I spent a large portion of the connectathon debugging a problem with loading conformance resources into the r4 endpoint of a hapi-fhir v3.3.0 server. Ended up filing a hapi-fhir pull request to fix the problem.
https://github.com/jamesagnew/hapi-fhir/pull/941

Joel Schneider (May 14 2018 at 08:25):

Also had a productive discussion with Rob Hausam covering various questions/topics/decisions related to representation of nomenclature-level HLA data.

Peter Jordan (Nov 21 2018 at 18:22):

@Rob Hausam , @Richard Ettema - one of the nice features of the Connectathon that HL7NZ held in Wellington this week was that the Terminology Services group provided key inputs to some of the other tracks - notably Provider Directory Services and Health Pathways. This is something that we've talked about in relation to the WGM Connectathons but have never really managed to put into action. Admittedly, it was easier to do with a small expert group (Michael Lawley & Jim Steel) at a smaller scale event - but, I think, definitely something that we should take a look at trying to achieve at the January Connectathon in San Antonio.

BTW - do we have another Stream/Thread for this Track - it surprised me to discover that the previous entry on this one was back on May 14th!

Rob Hausam (Nov 21 2018 at 18:45):

I totally agree that we should do this, @Peter Jordan (as you know). Maybe you can give a bit more update on how it was done and what was accomplished with it in Wellington? And whatever thoughts you or any of us have on how to make this happen with the other groups in San Antonio are certainly welcome. I think the first step is probably to reach out with something concrete to the other track leads (at least for the particular tracks where it makes sense) that they can be considering soon - and I think we would want to do that by mid-December (sufficiently prior to the holidays) at the latest. And, yes, this is the right stream/topic - we just didn't end up using it for anything for the September event (although I'm sure we should have).

Rob Hausam (Jan 12 2019 at 16:32):

We've scheduled a breakout at 1:00 PM to talk about handling "patient-friendly" terms - likely using code system supplements, but that's part of what we will be discussing. We will also be scheduling a breakout of the needed updates to ConceptMap, so stay tuned for that.

Peter Jordan (Jan 12 2019 at 16:43):

Please note that the latest versions of the test Value Sets & Concept Maps used by Touchstone aren't available in GitHub, so if anyone is still using the versions from Connectathon #19 in Baltimore please update the version attributes from C19 to C20.

Rob Hausam (Jan 12 2019 at 20:16):

We'll have the ConceptMap discussion at 4:00 PM today in Llano.

Senthil Nachimuthu (Jan 12 2019 at 20:22):

UCUM issue:
As I was mentioning in the breakout session, UCUM has two different codes for 'liter', as below. This is because they don't use nonsemantic concept identifiers and decided to create both codes (L and l) for liter.

<unit Code="l" CODE="L" isMetric="yes" class="iso1000">
<name>liter</name>
<printSymbol>l</printSymbol>
<property>volume</property>
<value Unit="dm3" UNIT="DM3" value="1">1</value>
</unit>

<unit Code="L" isMetric="yes" class="iso1000">
<name>liter</name>
<printSymbol>L</printSymbol>
<property>volume</property>
<value Unit="l" value="1">1</value>
</unit>

Rob Hausam (Jan 12 2019 at 20:29):

GF#19960 added for "consumer-friendly" terms

Senthil Nachimuthu (Jan 12 2019 at 20:35):

@Grahame Grieve Hi Grahame, the SI Brochure (chap. 4) lists both L and l as the symbols litre. They say, "The litre, and the symbol lower-case l, were adopted by the CIPM in 1879 (PV, 1879, 41). The alternative symbol, capital L, was adopted by the 16th CGPM (1979, Resolution 6) in order to avoid the risk of confusion between the letter l (el) and the numeral 1 (one)." So, I guess you and I read books that listed different symbols (rather than both) from SI. Ref: https://www.bipm.org/en/publications/si-brochure/chapter4.html (table 6)

Senthil Nachimuthu (Jan 12 2019 at 20:39):

This UCUM 'liter' issue is an excellent example/reason for why terminologies should use nonsemantic concept identifers (among many other reasons).

Grahame Grieve (Jan 12 2019 at 20:40):

interesting, thanks.

Grahame Grieve (Jan 12 2019 at 20:41):

long time since I've seen a standards reference that long ago

Chris Snyder (Jan 13 2019 at 14:56):

I've been working on our (very immature) terminology server during the connectathon. If anyone is interested in checking it out (feedback welcome), here's the URL: https://rosetta-connectathon.careevolution.com/api/FHIR/R4

Rob Hausam (Jan 13 2019 at 15:30):

Thanks very much, Chris. Any testing (formal or otherwise) and feedback on the CareEvolution server that anyone can provide will be much appreciated.

Rob Hausam (Jan 13 2019 at 15:32):

If everyone on the track can send me a brief note about what you worked on and accomplished yesterday and what you have done or expect to do today (by 2:00 PM) so I can include that in our track report, that would also be very much appreciated!

Rob Hausam (Jan 14 2019 at 13:56):

I've still been working to complete our Terminology Services track report. We had a rather productive and rather distributed track overall, I think. I've tried to include in the report all of the updates that were sent to me, but I'm pretty sure that I'm missing a least a couple of them. If all of you could take a look at the report (here) and add anything that is missing (particularly your own contributions and results) and correct anything that I didn't state correctly, that would be much appreciated. And if I missed including you in the list of participants, please add yourself there, too. Or if you prefer you can send any needed updates to me. Thanks for you participation and helping to make the track a success!

Chris Snyder (Jan 14 2019 at 15:18):

Thanks for your leadership, Rob!

Senthil Nachimuthu (Jan 14 2019 at 21:51):

Rob, thank you for organizing and leading the track.

Rob Hausam (May 04 2019 at 13:38):

Welcome to the Connectathon 21 Terminology Services track in Montreal - whether you are here in person or not! Please use this chat topic for any questions, issues, and progress on your activities over these two days. We'll be compiling all of that for our report at the end of the day tomorrow, so if you let me know here (or privately) or enter your activities and results in the ConMan tool directly, that will be great. Thanks!

Michael Lawley (May 04 2019 at 13:41):

The terminology server interactive testing tool I mentioned is here http://ontoserver.csiro.au/vstool Note, your terminology server needs to support CORS for it to be usable for your own server

Rob Hausam (May 04 2019 at 13:56):

I've scheduled the breakout session on Terminology Service Integration Strategies (my name for it) at 15:00 (3:00 PM) in Salon 1. Let me know if you are interested in being there (if we have more than 25 we can see about moving to the larger room).

Michael Lawley (May 04 2019 at 14:04):

For terminology authoring, the latest beta version of our tool is her https://ontoserver.csiro.au/snapper2-dev

Bertil Reppen (May 04 2019 at 14:12):

Allvaluesets.zip

Daniel Ye (May 04 2019 at 15:05):

ValueSets needed for Touchstone test scripts can be found here: https://touchstone.aegis.net/touchstone/testdefinitions?selectedTestGrp=/FHIR4-0-0-Connectathon21/Terminology-Formal/JSON%20Format/_reference&activeOnly=true&contentEntry=ALL

Jim Steel (May 04 2019 at 15:11):

Those seem to all be Parameters resources

Jim Steel (May 04 2019 at 15:12):

Ah, found them

Jim Steel (May 04 2019 at 15:19):

I think there's a bug in intensional case 1. It uses a LOINC filter of SYSTEM = Arterial system, but SYSTEM is code-typed, so it probably should be SYSTEM = LP7034-4

Grahame Grieve (May 04 2019 at 15:20):

LOINC have only recently assigned part codes - it should be part code based now that there are codes

Jim Steel (May 04 2019 at 15:21):

Yeah, that's what we implement, and I'm pretty sure the HAPI implementation does that now too

Grahame Grieve (May 04 2019 at 15:22):

mine won't - I have to update for that

Rob Hausam (May 04 2019 at 16:04):

We've moved up the breakout session on Terminology Service Integration Strategies to 14:00 (instead of 15:00) - still in Salon 1. Please invite anyone that you think should be there or would otherwise be interested in this discussion. We're going to talk about strategies for integrating FHIR terminology servers with other FHIR servers and leverage terminology services in applications, etc. (my summary - others feel free to add on). Michael Lawley and Jim Steel will talk about and show some of the work that they've done in Australia on this, particularly with leveraging the additional terminology capabilities of Ontoserver with the HAPI server.

Jim Steel (May 04 2019 at 19:41):

extensional-case-4 is now broken, because the URL of the v2 0001 CodeSystem has changed from http://hl7.org/fhir/v2/0001 to http://terminology.hl7.org/CodeSystem/v2-0001, but has not been updated in the extensional-case-4 ValueSet text fixture

Michael Lawley (May 04 2019 at 19:59):

FHIR-Servers-and-externalised-Terminology.pptx -- slides from the breakout

Jim Steel (May 04 2019 at 20:44):

some terminology service samples using HTML/Javascript https://aehrc.github.io/fhir-ts-exemplars/

Richard Ettema (May 05 2019 at 11:09):

@Jim Steel, I will update the fixtures and ValueSet validate-code TestScripts this morning. Thanks.

Jim Steel (May 05 2019 at 12:55):

Intensional case 3 is tricky. All SNOMED clinical findings is a lot of findings (111777 in the latest Australian edition), so I'd argue its reasonable if a server responds with Too Costly. It might be worth finding a more manageable subhierarchy to use as an intensional definition

Richard Ettema (May 05 2019 at 13:11):

I have corrected the extensional-case-4 ValueSet and corresponding TestScripts to now reference the correct code system -
http://terminology.hl7.org/CodeSystem/v2-0001. The updates have been committed to the FHIR/documents Github repo and uploaded to Touchstone.

Bertil Reppen (May 05 2019 at 13:32):

https://r4.ontoserver.csiro.au/fhir/ConceptMap/$translate?system=http://hl7.org/fhir/address-use&code=home&source=http://hl7.org/fhir/ValueSet/address-use&target=http://terminology.hl7.org/ValueSet/v3-AddressUse

Bertil Reppen (May 05 2019 at 18:04):

http://conman.clinfhir.com/connectathon.html?event=montreal2019

Jim Steel (May 05 2019 at 18:48):

The oracle for Test: Test 02-b Validate extensional-case-2 valid code invalid display states that ...

Minumum '/Parameters/parameter[2]/name' value of 'message' could not be found in response.
Description: Confirm that the returned Parameters minimally contains the information in validate-code-invalid-min.

This is too brittle (for example, we report 'message' as the third parameter in the response)

Jim Steel (May 05 2019 at 18:51):

same for 3b, 4b, 5b (we are inadvertently passing this because the intensional-1 ValueSet is broken) 6b, 7b

Jim Steel (May 05 2019 at 18:55):

Hmm, actually, this pattern is all over the place

Michael Lawley (May 05 2019 at 19:06):

More work for @Richard Ettema :-)

Grahame Grieve (May 05 2019 at 19:23):

yes is anyone tracking all this?

Richard Ettema (May 05 2019 at 20:43):

Got it. I'll make it less "brittle". ;)

Rob Hausam (Sep 14 2019 at 11:42):

The Terminology Services track is having a breakout session this morning in M103 at 10:00 AM on Terminology Services Support for SNOMED CT. Supporting the implementation and use of SNOMED CT is a major focus for this Connectathon. This breakout is for all of you in any track who uses or needs to use SNOMED CT (yes, that's pretty much everyone!). So if at least one from every track could attend (subject to room limits!), that would be great. We would like to hear about your needs and experiences and frustrations, and intend to offer help and suggestions for meeting your needs during this session and this weekend. We're focusing on SNOMED CT as it's the most complex and broadly useful clinical terminology and nearly everyone needs and uses at least a part of it, but what we will cover likely applies to most other terminologies, as well. The effort during this Connectathon is in alignment with and supported by the work being done in the Terminology Services stream of the joint SNOMED on FHIR project of SNOMED International and HL7, which is producing a SNOMED on FHIR FHIR IG (so stay tuned for that).

Tim Briscoe (Sep 14 2019 at 13:31):

LOINC test server https://fhir-dev.loinc.org (It does require a free LOINC user account that can be obtained at https://loinc.org/join ) NOTE: this development TS contains unreleased LOINC terms. Use with caution.

Rob Hausam (Sep 14 2019 at 14:04):

Join us now in M103 for the Terminology Services Support for SNOMED CT breakout.

François Macary (Sep 14 2019 at 14:59):

I attended. Thank you for the discussion.

Oliver Egger (Sep 14 2019 at 14:59):

thx for the discussion!

Rob Hausam (Sep 14 2019 at 19:38):

This is a friendly reminder to all of us (myself included) to fill out what we're doing in the ConMan tool so we will have a record of our activities for the report at the end of the day tomorrow.

Rob Hausam (Sep 14 2019 at 19:46):

Sorry, I posted the wrong url for ConMan before - fixed now.

David Hay (Sep 14 2019 at 20:35):

And apologies that I didn't set this up before the event - Peter J is kindly correcting that for me...

Rob Hausam (Sep 14 2019 at 22:34):

We have scheduled a breakout on Resource instance and "closest match" terminology translation at 9:00 AM in M101 - these are questions/scenarios from Chris Grenz.

François Macary (Sep 15 2019 at 12:55):

It's just a matter of finding the way in Conman to assign scenarios to a system and to enter results. Haven't succeded yet.

François Macary (Sep 15 2019 at 15:51):

Thanks to @Peter Jordan we found out how to record the results. In the "Technical testing" tab:
Choose your scenario in the list.

• Add client, select the client you want, assign it to the role you want and then add it
• Do the same for the server
• Then a "Result" paragraph pops up, in which you can record the results of the test.

Rob Hausam (Feb 01 2020 at 22:15):

We'll use this stream again for the Terminology Services track at the Connectathon here in Sydney today and tomorrow. Feel free to ask questions or post anything of interest to the group. We'll look at scheduling one or more breakouts shortly.

Peter Jordan (Feb 01 2020 at 22:26):

Value Set Comparison Tool .. http://ontoserver.csiro.au/vstool/

Peter Williams (Feb 01 2020 at 22:27):

The SNOMED on FHIR group have suggested using a token in a designation as a way of passing in a (SNOMED) Language Reference Set ID which allows for recovering dialects (eg en-US) as well as community type dialects like patient friendly terms. In the Snowstorm implementation it then seemed like a good idea to also allow includeDesignations=false to work in line with that to cut the response down to a minimum so you can recover just the term you need as the display value. I'd like to discuss this further. Example: https://dev-fhir.snomedtools.org/fhir/ValueSet/$expand?url=http://snomed.info/sct?fhir_vs=ecl/322280009&designation=http://snomed.info/sct|900000000000509007&includeDesignations=false

Rob Hausam (Feb 01 2020 at 23:31):

We've scheduled a SNOMED on FHIR terminology services breakout in C3.1 at 11:30 - 12:30. Topics to cover include URIs, designations, properties on $expand, recent ConceptMap changes (time permitting - we'll schedule additional breakouts as needed).

Rob Hausam (Feb 01 2020 at 23:34):

Re-posting the link to Peter's FHIR Server Available post here.

Danielle Friend (Feb 02 2020 at 00:24):

Here is our endpoints for our valueset APIs - right now we support $expand for the following two data elements if anyone wants to try them out:
Note: We do expect the following request header to be provided for testing (Epic-Client-ID: ArgoAAAA-A0be-4d9c-bb49-000000000000)
DocumentReference.type
https://connectathon.epic.com/Interconnect-Fhir-Argonaut/api/FHIR/R4/ValueSet/$expand?context=DocumentReference.type&contextDirection=incoming&filter=category:clinical-notes
DocumentReference.docStatus
https://connectathon.epic.com/Interconnect-Fhir-Argonaut/api/FHIR/R4/ValueSet/$expand?context=DocumentReference.docStatus&contextDirection=outgoing&filter=category:clinical-notes

Example postman request with header pasted image

Rob Hausam (Feb 02 2020 at 20:58):

I've added a breakout session on ConceptMap (for the latest completed / proposed updates to relationships and otherwise) this morning at 10:00. Let me know if that does / does not work for you. I have it on the schedule now to immediately following the FHIR / VS (V2?) Mapping breakout in C3.2 (so that hopefully it will work for Grahame and others who will be in that session).

Rob Hausam (Feb 02 2020 at 22:51):

For everyone doing work in this track, if you can send me brief note(s) on what you've done or still working on yesterday and today, that would be most helpful for the track report for this afternoon. Thanks!

Peter Williams (Feb 02 2020 at 23:39):

How would you like to receive that @Rob Hausam , public / PM / email?

Rob Hausam (Feb 03 2020 at 01:36):

Any of those would be fine, Peter.

Rob Hausam (May 13 2020 at 04:37):

Hi, everyone! We'll use this stream again for the Terminology Services track in the Virtual Connectathon beginning a little under 17 hours from now. We are planning to have a track opening meeting tomorrow at 5:00 PM Eastern, immediately following the end of the Connnectathon Kick Off Call. We'll be using the Zoom meeting here for that and all of our other track sessions. The track Confluence page is here. We'll try to get that updated and keep it up to date with relevant details, including breakout sessions. We'll do some planning for the breakouts during our opening meeting tomorrow, to figure out a schedule that will work for most (or hopefully all) of us. Feel free to ask any questions or post anything that will be of interest to the group here. We'll see you virtually tomorrow!

Peter Jordan (May 13 2020 at 04:43):

@David Hay When time permits :) would it be possible to copy into ConMan the scenarios for the Terminology Services track from either the Sydney or Atlanta WGM versions? Many thanks in advance!

David Hay (May 13 2020 at 04:50):

For you, of course! Will do that after the opening session tomorrow - a bit busy right now...

Rob Hausam (May 13 2020 at 19:37):

This is a follow on reminder and update to everyone in the Terminology Services track. As I mentioned last night, we are planning to have our track opening meeting today immediately following the Connnectathon Kick Off Call - but it looks like the time for our meeting is going to be 5:30 PM Eastern, since the Kick Off has been scheduled for 90 minutes. Looking forward to talking with (and probably seeing, at least initially) all of you then.

Peter Jordan (May 13 2020 at 19:54):

For those interested in viewing COVID-19 related concepts...
https://covid19ia.org/browser/ - COVID-19 Interoperability Alliance (has US SNOMED CT extensions)
https://terminz-itp.azurewebsites.net/Home/Covid - Patients First/HL7NZ Terminology Server Client

Peter Jordan (May 13 2020 at 20:27):

Rob - can we start earlier as it looks as if the KO meeting is going to end shortly?

Rob Hausam (May 13 2020 at 20:27):

It looks like we will be able to start our meeting much earlier than we had expected. I'll go ahead and open the Zoom meeting and we can start shortly - as soon as the questions have finished.

Rob Hausam (May 13 2020 at 23:01):

We are having a breakout session on NamingSystem at 7:30 PM Eastern (00:30 UTC). We intend to discuss the purpose and use of NamingSystem, and answer some questions that are being asked regarding when (or whether) to use it vs. CodeSystem, etc.

Rob Hausam (May 13 2020 at 23:12):

Here are the slides for the FHIR Terminology tutorial/webinar for @Arun Kumar and whoever else would like to have them. FHIR-Terminology.pptx

Peter Jordan (May 14 2020 at 04:20):

I've just added all the Touchstone Testing Scenarios to ConMan and some results.

Arun Kumar (May 14 2020 at 06:11):

Rob Hausam said:

We are having a breakout session on NamingSystem at 7:30 PM Eastern (00:30 UTC). We intend to discuss the purpose and use of NamingSystem, and answer some questions that are being asked regarding when (or whether) to use it vs. CodeSystem, etc.

Thank you Rob for the slides.

Arun Kumar (May 14 2020 at 06:15):

What is the difference between preferred and extensible binding strength. Please explain the scenario for a diagnosis code where ICD is the first choice and NANDA is second.

Peter Jordan (May 14 2020 at 07:30):

Binding Strengths R4 spec

Lloyd McKenzie (May 14 2020 at 13:22):

You'd have to create a single value set with all of the ICD10 codes and then additional NANDA codes for things ICD10 doesn't cover. There's no ability in FHIR to say "we'd like you to send ICD10, but if you can 't, then we'll take NANDA". The best you could do is two optional slices on CodeableConcept.coding each with a 'required' binding and an invariant that requires one or the other.

Rob Hausam (May 14 2020 at 13:24):

@Arun Kumar Does the binding strength page that Peter posted answer your question (at least part of it)?

Arun Kumar (May 14 2020 at 13:26):

Yes. It did.

Rob Hausam (May 14 2020 at 13:27):

@Lloyd McKenzie I took Arun's question as probably more about utilizing multiple Codings in a CodeableConcept as "translation" codes? Being able to send both an ICD10 code and a NANDA codes with the same meaning (allowing for differences in granularity between code systems)? But there's no notion of "first choice" and "second choice" with that.

Rob Hausam (May 14 2020 at 13:35):

Just a reminder (or a notice, if you didn't see or hear about it earlier) that we are planning to have a track meeting on Zoom beginning at 10:15 AM Eastern (14:15 UTC), following the FHIR Overview session. We'll touch base with all of us and talk about what is planned for today (in US time, anyway), including planning for more of our breakout sessions, and answer questions or anything else that is needed.

Rob Hausam (May 14 2020 at 16:11):

FHIRPath expressions and terminology access breakout is happening on Zulip now.

Rob Hausam (May 14 2020 at 17:02):

Newcomers breakout session is happening on Zulip now.

Rob Hausam (May 14 2020 at 18:21):

Passing this along to the group from Arun Kumar (originally on the Zoom chat). A suggested plan for further or future Terminology Services Track introduction session(s):

Suggested Plan
- Use Onto server to run test plans.
- Document my results in Conman.
- Use Postman/ Touchstone/ Browser as the client.
- Testscripts as per https://confluence.hl7.org/display/FHIR/2020-05+Terminology+Services+Track


We didn't get into this kind of information during our newcomer's session that just ended, and it does seem that these more track-specific details would likely be very useful for people. We could do this in another session today or tomorrow, or try to answer and do some of it asynchronously (here on Zulip, or otherwise). Please post your thoughts.

Rob Hausam (May 14 2020 at 19:51):

We're planning a Newcomers session - Part 2 breakout session at 6:30 - 7:30 PM Eastern (22:30 - 23:30 UTC) today (following our Federated terminology services session, with a short break between). Suggested topics are use of ConMan, Touchstone and TestScripts, Postman and browsers as clients, available FHIR terminology servers, etc.

Michael Lawley (May 14 2020 at 22:01):

For those interested in browsers as clients, these links may be of interest:
http://snomed.org/ui -- code @ https://github.com/aehrc/snomed-ui
https://aehrc.github.io/fhir-ts-exemplars/ -- code @ https://github.com/aehrc/fhir-ts-exemplars

Rob Hausam (May 14 2020 at 22:23):

Any chance you have a few minutes to join and explain, @Michael Lawley?

Michael Lawley (May 14 2020 at 22:27):

I'm just about to go into a work meeting here. I'll try to join in a bit later.

Briefly, the first one is a demonstration of real-time code search/selection using ValueSet/$expand with the filter parameter.
There's some extra stuff in there like checking for whether the selected code is lateralizable and conditionally allowing left/right/both to be specified and also pre-populating the field if the concept already caries that information.

The second one is kind of a grab-bag of demonstrating different things you can do with the Terminology Services API.

Rob Hausam (May 14 2020 at 22:28):

Thanks.

Michael Lawley (May 15 2020 at 00:19):

I guess the zoom's not running now

Peter Jordan (May 15 2020 at 01:05):

@Michael Lawley we would schedule something for later if you and Rob are available around 02:00 UTC. I'm just about to go out for 30 mins.

Rob Hausam (May 15 2020 at 05:04):

Just saw this. Would 11:00 UTC work for you guys? It's quite late for Peter, but I should be able to get up that early if that will work.

Michael Lawley (May 15 2020 at 05:04):

I could do a bit later -- I'll be doing family taxi service until about 11:30 UTC

Rob Hausam (May 15 2020 at 05:05):

I guess we had a similar problem. :)

Rob Hausam (May 15 2020 at 05:07):

It will be 11:30 PM for Peter, but I could do that.

Rob Hausam (May 15 2020 at 05:11):

Or, if we want to do it right now, I suppose I could do that, too - I'm still up. :) @Peter Jordan @Michael Lawley

Michael Lawley (May 15 2020 at 05:13):

I'm available for the next hour

Peter Jordan (May 15 2020 at 05:13):

Right now would suit me - I won't be awake after 10:30 UTC

Rob Hausam (May 15 2020 at 05:14):

ok, let's do it

Grahame Grieve (May 15 2020 at 05:18):

what's the link?

Grahame Grieve (May 15 2020 at 05:19):

found it

Michael Lawley (May 15 2020 at 06:01):

For an example of terminology services used from FHIRPath people could look at https://pathling.csiro.au/ which is an open source project aimed at exploiting FHIRPath with an external terminology server for analytics.

Rob Hausam (May 15 2020 at 13:18):

Hi, everyone. I think we all had a great and rather full day yesterday (depending on your time zone). I had thought that we would have a track session again now following the opening session, but I have a different contract meeting that that I've ended up needing to attend right now, until the top of the hour. We can group again after that, or virtually here as we have been.

Rob Hausam (May 15 2020 at 13:35):

When it gets to be afternoon (US time) I want to encourage all of us to enter our activities and results in ConMan, or post them to Zulip (here or privately), and I will work on pulling it all together into our track report.

Rob Hausam (May 15 2020 at 14:34):

Another item - if everyone can check our track Confluence page and make sure that your name is in the list of Participants. You can either edit the page directly, or send the information to me, if you prefer. It would also be good to include your affiliation and location (I'll see about reorganizing the list as a table to facilitate that). I want to be sure that we don't miss anyone who has been participating in the track - in whatever way you have been doing that.

Rob Hausam (May 15 2020 at 15:07):

I've started the Zoom meeting. I suggest that we meet (as many of us who can) at the top of the hour (11:30 AM Eastern) for probably 30 min. and talk about plans for the track for the rest of the day. There are a few additional breakout sessions that we were considering, and if we are going to do that we need to schedule them ASAP. I'm also going to post the recordings from our sessions over the past 2 days. In the meantime the Zoom meeting is open for general chat and questions or comments.

Rob Hausam (May 15 2020 at 17:31):

We've scheduled a breakout on Handling pre-release codes (e.g. LOINC, SNOMED CT) and using code system fragments from 4:30 - 6:00 PM Eastern (20:30 - 22:00 UTC). We can take up to the full 90 minutes, if we need it - and that will take us up to the final "Connectathon 24 Wrap Up" session at 6:00 PM. And a heads up on that for the Australia/New Zealand contingent: @Grahame Grieve @Michael Lawley @Peter Jordan - who should be sleeping now, but maybe not? :)

Peter Jordan (May 15 2020 at 18:00):

Sounds good!

François Macary (May 15 2020 at 20:13):

Short report from PHAST: This time we spent more time on the catalog track, however our terminology server STS passed the terminology touchstone tests today, with 98% success... Saving the last 2% for connectathon #25 :yum: Thanks.

Sarah Tonn (May 15 2020 at 22:47):

To @Rob Hausam and @Peter Jordan --Thank you very much for serving as Terminology Services Track leads. The Connectathon-24 'first-timer' experience was impressionable. The Terminology Services work is extensive, meaningful, and crosses all areas of the healthcare interoperability FHIR framework. Thank you for the many contributions to both of you and so many of the others within this track and beyond. Many really appreciate the brain power for the public good.

Rob Hausam (May 15 2020 at 22:47):

Thanks to everyone for being part of this. We especially appreciate the new participants, and hope that overall you had a good and useful experience. Overall, I think it was really amazing. It was definitely different from what we've done before - and we all learned a lot. We'll certainly have some things that we've learned and experiences that we can bring forward to our future Connectathon events (whether virtual, or in-person, or a combination of those). This time I think we ended up with the emphasis leaning more than usual toward discussion and education, and probably less actual connecting. In the future maybe we can strike a something more even balance on that - now that we have a better idea of how that might work in this environment - we do have a lot of things that we need to test, so we'll definitely be working on that. Please fill out the survey and provide any other feedback that you have, here or directly to me or Peter or anyway that works. I've already heard the suggestion that each Connectathon track should have its own Zulip stream, so we can have multiple topics and have easier and more consistent visibility. I had already thought that we should probably do that, and I think we'll go ahead and set that up and will announce that generally and here when that is ready - and then we can continue to "connect" and share our thoughts, ideas and questions until the next time. Thanks again for helping to make our track and this Connectathon event a great success!

Peter Jordan (May 15 2020 at 23:11):

Thanks for your feedback, @Sarah Tonn - much appreciated. It would be good to hear suggestions about any improvements we might make for the next Virtual Connectathon.

Peter Jordan (Sep 08 2020 at 23:45):

I propose that we continue to use this thread for C25, rather than create a new one. Is everyone agreeable to that? @Rob Hausam @Robert McClure @Carol Macumber @Daniel Karlsson @Ward Weistra

Carol Macumber (Sep 08 2020 at 23:49):

Yup, works for me

Peter Jordan (Sep 09 2020 at 03:14):

@Rob Hausam and I are planning to host a Track Orientation Meeting directly after the Event Kick-Off. Because of 'international' participation, this track is likely to run 24/7 for the duration of the Connectathon.

Mary Ann Boyle (Sep 09 2020 at 12:05):

@Sandra Vance Please let @Bryn Evans and I know what we need to do to help @Peter Jordan with this request for 24/7 meeting right after the kick off

Bryn Evans (Sep 09 2020 at 13:43):

@Peter Jordan Would you like this evenings Zoom session to appear in Whova?

Sandy Vance (Sep 09 2020 at 15:20):

Bryn Evans said:

Peter Jordan Would you like this evenings Zoom session to appear in Whova?

Bryn - hours - if edited - would be for the Terminology Track

Bryn Evans (Sep 09 2020 at 16:35):

@Dennis Patterson I just sent you an email through Whova, see if that lets you edit your Session info.

Peter Jordan (Sep 09 2020 at 19:30):

@Bryn Evans - yes please.

Bryn Evans (Sep 09 2020 at 19:44):

@Peter Jordan Your session is created for tonight. Let me shoot you an email with your Zoom info as well, just in case.

Peter Jordan (Sep 09 2020 at 19:55):

Hope that everyone has the Zoom Address and Credentials for the Track Orientation Meeting directly after the Event KO.

Bryn Evans (Sep 09 2020 at 20:45):

Hey @Bill Lober I hear you're having trouble accessing your sessions

Davera Gabriel (Sep 09 2020 at 20:48):

Hello all: can I get more info about the terminology services session happening today?

Peter Jordan (Sep 09 2020 at 20:48):

We need to be able to access this session via Whova now - otherwise, I'll have to post the Zoom details on here.

Davera Gabriel (Sep 09 2020 at 20:49):

Ok - Im am new to all of this - how do I access this via Whova?

Davera Gabriel (Sep 09 2020 at 20:50):

Can I get info sent privately to me in a message on Whova?

Peter Jordan (Sep 09 2020 at 20:52):

Go to the Agenda and click the relevant View Session link...the TS one isn't active yet.

Davera Gabriel (Sep 09 2020 at 20:52):

thank you @Peter Jordan

Robert McClure (Sep 09 2020 at 20:59):

I'm on a plane and will join at 38,000 feet, with chop I'm sure

Peter Jordan (Sep 09 2020 at 22:52):

Confluence Site for this Track...
https://confluence.hl7.org/display/FHIR/2020-09+Terminology+Services+Track

Swapna Abhyankar (Sep 09 2020 at 23:26):

Hi - I'm interested in code system versioning, including pre-release; ConceptMap; and designations (incl. language variants and consumer-friendly names).

Daniel Karlsson (Sep 10 2020 at 07:19):

Hi all (greetings from CEST), when is the next TST event?

Peter Jordan (Sep 10 2020 at 08:26):

Hi @Daniel Karlsson - next TS session is at 09:00 EST (13:00 UTC) on Sept 10th. Rob Hausam will be leading that; I'll probably be there 4-5 hours later.

Daniel Karlsson (Sep 10 2020 at 13:01):

Am I in the right place at the right time?? "The host has not started the Zoom stream yet."?

Davera Gabriel (Sep 10 2020 at 13:03):

Hello! How do I find the Term services session in Whova or Zoom?

Davera Gabriel (Sep 10 2020 at 13:03):

is Zoom better?

Daniel Karlsson (Sep 10 2020 at 13:03):

https://whova.com/portal/webapp/hlfhi_202009/Agenda/1226671
or so I believe...

Daniel Karlsson (Sep 10 2020 at 13:03):

I think Zoom is embedded in Whova...

Davera Gabriel (Sep 10 2020 at 13:04):

Thank-you @Daniel Karlsson

Rob Hausam (Sep 10 2020 at 13:04):

The Zoom meeting is started now.

Rob Hausam (Sep 10 2020 at 13:04):

We are supposed to get to it through Whova. And that should work. :)

Davera Gabriel (Sep 10 2020 at 13:04):

@Rob Hausam is it the same url as the session form last night?

David Johnson (Sep 10 2020 at 13:05):

Daniel, it will not be on google drive. Sandy Vance is adding it to confluence by noon

David Johnson (Sep 10 2020 at 13:05):

Rob is currently talking on the terminology services track

David Johnson (Sep 10 2020 at 13:05):

There are 9 participants

David Johnson (Sep 10 2020 at 13:06):

You should be able to access it by clicking on agenda in Whova

David Johnson (Sep 10 2020 at 13:07):

11 participants in terminology services track

David Johnson (Sep 10 2020 at 13:07):

I am showing @Daniel Karlsson as a participant. I think we're good.

Ryan Short (Sep 10 2020 at 13:19):

@Rob Hausam We have a instance of our terminology server accessible for anonymous access at https://connectathon.healthterm.com/fhir

Daniel Karlsson (Sep 10 2020 at 13:22):

@Ryan Short HealthTerm asks for user/password!

Ryan Short (Sep 10 2020 at 13:22):

The API is anonymous, the UI needs a username/password. I'll need to grab the UI user/pass
Credentials: cadmin / cadmin

Ryan Short (Sep 10 2020 at 15:05):

https://r4.ontoserver.csiro.au/fhir/metadata?mode=terminology

François Macary (Sep 10 2020 at 17:06):

I've got a question related to one Touchstone test on NamingSystem/$preferred-id. I'll raise it on the terminology stream. Seems more appropriate than here.

Rob Hausam (Sep 10 2020 at 18:27):

In case anyone missed it, we are currently in the NamingSystem breakout session at https://zoom.us/j/7183806281?pwd=WHVnUUlkWWhhcnRaYk9sWWQyOEkvUT09.

Rob Hausam (Sep 10 2020 at 19:52):

The Designations (multiple languages, consumer-friendly, etc.) breakout session is starting at the top of the hour at 4:00 PM Eastern / 20:00 UTC at https://zoom.us/j/7183806281?pwd=WHVnUUlkWWhhcnRaYk9sWWQyOEkvUT09.

Richard Ettema (Sep 10 2020 at 20:38):

FYI - For anyone testing in Touchstone and running the new NamingSystem $preferred-id TestScripts, Francois found that the Parameters fixtures for the request payload incorrectly defined the parameter value types. The fixtures have been corrected and uploaded to Touchstone.
Thanks Francois for catching that.

Rob Hausam (Sep 10 2020 at 21:47):

Our last breakout session today is ConceptMap - R5 updates and issues planning for R4B / R5 release starting on 13 minutes at 6:00 PM Eastern / 22:00 UTC at https://zoom.us/j/7183806281?pwd=WHVnUUlkWWhhcnRaYk9sWWQyOEkvUT09.

Rob Hausam (Sep 11 2020 at 12:59):

If it's OK with everyone I would like to start our "official" morning (US) session after 9:30 AM Eastern / 13:30 UTC, as I need to catch up with my other track. We'll plan our remaining breakout sessions for today, so you can be thinking about that (they are listed in Confluence), and post any additional suggestions or questions in the meantime. Peter Jordan should be joining us again at about 2:00 PM Eastern / 18:00 UTC.

François Macary (Sep 11 2020 at 14:18):

Report on Terminology track: PHAST STS server passed the TouchStone /FHIR4-0-1-Connectathon25/Terminology-Formal battery of tests with 99% success.
The two tests we failed are $validate-code with SNOMED CT for which our server currently returns the FSN instead of the en-US preferred synonym. We are aware we need to correct this behavior, however it's related to our data model so it will take a few days. Should be corrected next week.
For this connectathon we are satisfied with the 99% score.

Peter Jordan (Sep 11 2020 at 16:47):

I'm back and awake (just).

Rob Hausam (Sep 11 2020 at 17:58):

The breakout session on Code System and Value Set Versioning (pre-release codes) is starting now at https://zoom.us/j/7183806281?pwd=WHVnUUlkWWhhcnRaYk9sWWQyOEkvUT09.

Rob Hausam (Sep 11 2020 at 19:54):

Following a rousing breakout session on Code System and Value Set Versioning (pre-release codes), our next and final one on TerminologyCapabilities (maturity, use, etc.) will be starting in 6 min. at the top of the hour at https://zoom.us/j/7183806281?pwd=WHVnUUlkWWhhcnRaYk9sWWQyOEkvUT09.

Ryan Short (Sep 11 2020 at 21:04):

Report for Terminology track: Attending our first Connectathon HealthTerm server managed to obtain 77% from the /FHIR4-0-1-Connectathon25/Terminology-Formal tests.
The failing tests fell into three groups. About 10% are related to incorrectly sending OperationOutcome responses for some validate-code tests rather than Parameters, these should be a quick fix next week. 1-2% related to how we're representing Intensional ValueSet resources. The remaining 10-12% are for items related to our data model, particularly around versions, which will require more investigation.
We're quite happy with where we got to at this Connectathon and it's given us a good fixed list of remaining items to focus on.

Ankita Srivastava (Jan 04 2021 at 09:32):

@Rob Hausam Hello Rob, I have participated in FHIR Connectathon (Terminology track) and would like to participate in pre-connectathon activities (if any). Please advise on the same. Thank you

Michael Lawley (Jan 12 2021 at 21:46):

"intensional-case-3" in the test /FHIR4-0-1-Connectathon26/Terminology-Formal/JSON Format/Expand/terminology-expand-json is incorrectly reporting an error in the terminology server under test when the server returns a response > 500 000 bytes which is then rejected by Touchstone itself.
image.png

Michael Lawley (Jan 12 2021 at 21:50):

"SNOMED-LookupDrugInteraction" in /FHIR4-0-1-Connectathon26/Terminology-Formal/JSON Format/Lookup/terminology-lookup-sct-01-ok-get-simple-json incorrectly limits the set of valid display values for 79899007. SNOMED AU has the preferred term "Medicine interaction"

Michael Lawley (Jan 12 2021 at 21:52):

/FHIR4-0-1-Connectathon26/Terminology-Formal/JSON Format/Lookup/terminology-lookup-sct-02-ok-post-code-simple-json
/FHIR4-0-1-Connectathon26/Terminology-Formal/JSON Format/Lookup/terminology-lookup-sct-03-ok-post-coding-simple-json
have the same error

Michael Lawley (Jan 13 2021 at 03:11):

/FHIR4-0-1-Connectathon26/Terminology-Formal/JSON Format/Translate/terminology-translate-01-ok-get-json is mis-described.
Specifically, the text "ConceptMap $translate tests against known FHIR code systems" is inaccurate -- this test operates on unknown ConceptMaps, although the anticipated maps do reference "known" CodeSystems.

I say unknown here because the invocation of $translate is at the type level and does not specify a specific ConceptMap to be used (so there are no guarantees of behaviour.

Carie Hammond (Jan 13 2021 at 17:06):

Michael - the Touchstone team has already been looking at addressing the response size and are hoping to increase our acceptable response size as well as handle any tests which receive that issue more gracefully. We can also take your comment on the Terminology tests back to our test developers and see if those tests need some corrections. I will ensure your concerns are logged in our tracker.
Please note, if you have further questions or concerns on Touchstone, we have a stream at #Touchstone or you can also contact us at touchstone_support@aegis.net for immediate response. Thank you for using Touchstone! - Carie

Gabriel Kleinoscheg (Jan 13 2021 at 23:58):

@Carie Hammond This is the first time I'm participating at a FHIR Connectathon. I found my way around to the Touchstone testscripts that are provided for the terminology track. I now wondered if you could help me finding the definition of the ValueSets and CodeSystems that are being tested - i.e. the corresponding resources.

Peter Jordan (Jan 14 2021 at 00:01):

https://confluence.hl7.org/display/FHIR/2021-01+Terminology+Services suggest attending the TS Track KO meeting at 5PM PST

Carie Hammond (Jan 14 2021 at 00:32):

@Gabriel Kleinoscheg those terminology tests actually do lookups by the resource name that houses that information (like ValueSet). They are meant for terminology servers. If you aren't sure by the test name, all our tests have hyperlinks to the actual test body, which is a TestScript resource (which makes it fairly easy to navigate - though the 'description' elements inside also assist). You will find some additional information inside the test as well as you can look at the operations and resources that the test is using). I hope that helps, but please let us know if you have additional questions and we can look to find you the appropriate tests you need.

Gabriel Kleinoscheg (Jan 14 2021 at 00:47):

@Carie Hammond Thank you for your answer! I get the idea of the scripts. Taking the following script for example /FHIR4-0-1-Connectathon26/Terminology-Formal/JSON Format/Validate-ValueSet/terminology-valueset-validate-code-json - where is the ValueSet extensional-case-1 specified?

Peter Jordan (Jan 14 2021 at 00:49):

Servers also need to have the test Value Sets, Concept Maps and Naming Systems (if they wish to have their implementation of those resources tested) and support the SNOMED CT and LOINC Code Systems.

Peter Jordan (Jan 14 2021 at 00:53):

@Carie Hammond this link to the Terminology Services Test Content Resources is broken - could you please provide an updated link asap.

https://github.com/FHIR/documents/tree/master/connectathons/VirtualSept2020/FHIR4-0-1-Connectathon26/Terminology-Formal

Richard Ettema (Jan 14 2021 at 00:58):

@Peter Jordan, I will be committing the C26 Terminology TestScripts to GitHub after I'm done with my FHIR Overview presentation tonight.

Peter Jordan (Jan 14 2021 at 00:58):

Many thanks - my bad, I should have tested that link before today!!

Gabriel Kleinoscheg (Jan 14 2021 at 00:59):

Thank you guys!

Brian Walsh (Jan 14 2021 at 01:17):

Can't login to confluence

Mary Ann Boyle (Jan 14 2021 at 01:30):

@Joshua Procious can you please help @Brian Walsh

Carie Hammond (Jan 14 2021 at 01:36):

@Gabriel Kleinoscheg - if you open that testscript, you will see that a few places. The first is the description of each test inside the testscript - such as: <description value="Check that the code {http://hl7.org/fhir/administrative-gender}male is in the value set."/> - and if you look at the operation for that test, you will see some of the params used in the test operation also offer some insight: <params value="/extensional-case-1/$validate-code?system=http://hl7.org/fhir/administrative-gender&code=male"/>

This tends to be much easier to see if you run the test - even if you run it against a server that fails the test, as you can use the status icons from the test results (the pass or fail bars) which are hyperlinks to continue to dig down into the test and see each test, each test assertion, and even the details of the operations that are helping to exercise the server under test. Also, any time you see '...' you can click on that to open even farther into the test output details - including the request details down to the request path, any headers, response information and the actual response body (or request body if there was one in a test).

Ankita Srivastava (Jan 14 2021 at 16:03):

@Robert McClure/ @Rob Hausam Kindly share the link for next session for Terminology track

Sandy Vance (Jan 14 2021 at 16:04):

Ankita Srivastava said:

Robert McClure/ Rob Hausam Kindly share the link for next session for Terminology track

Hi Ankita! You will need to go in through Whova. At the top of the page filter by Terminology Services and you will see all the sessions for this track.

Ankita Srivastava (Jan 14 2021 at 16:07):

@Sandra Vance Thank you for your response... I have already used the filter but it seems nothing has been planned after UTG session.

Sandy Vance (Jan 14 2021 at 16:11):

Ankita Srivastava said:

Sandra Vance Thank you for your response... I have already used the filter but it seems nothing has been planned after UTG session.

The next session is at 11:00 AM PT. Please take another look as there were recently updated.

Ankita Srivastava (Jan 14 2021 at 16:16):

Thank you so much @Sandra Vance .. got the updated timelines. Thanks

Rob Hausam (Jan 14 2021 at 16:32):

@Ankita Srivastava So do you have what you need now?

Ankita Srivastava (Jan 14 2021 at 16:40):

@Rob Hausam Yeah.. I do have the updated details now.. thank you so much

Rob Hausam (Jan 15 2021 at 04:13):

I've adjusted the time for our Office hours "Ask the expert" Q&A session tomorrow to 11:00 - 12:30 PM PT (instead of 11:15 - 12:15 PM). The conflict that we thought we had that caused us to start 15 minutes later isn't really there, and we can also go a little longer up until the track highlights session begins at 12:30. I do have a conflict and will need to be in an IPS session for the first 60 minutes, but we should have other "experts" there and I'll plan to join for the last part. And finally, also in order to avoid conflicts with IPS I've taken the liberty to request both rescheduling and shortening our Terminology Services track wrap-up session and moving it to 3:30 - 4:00 PT. That's just before the final wrap-up session for the Connectathon itself, and I hope that won't cause a problem for anyone. Will talk tomorrow!

Peter Jordan (Sep 07 2021 at 07:44):

Thanks @Richard Ettema for putting the C28 Terminology Services Tests up on Touchstone. I've just run them against Terminz and all passed ok. @Rob Hausam and @Davera Gabriel FYI.

Davera Gabriel (Sep 07 2021 at 18:41):

thank-you for doing that @Peter Jordan

Last updated: Apr 12 2022 at 19:14 UTC