Page tree
Skip to end of metadata
Go to start of metadata

Call Information

Ways to Join

Go to: or just call 202-871-0098 . No PIN needed.




XConformance Cochair (chair/scribe)
XConformance Cochair
XPublic Health Cochair
XConformance Cochair


Conformance Cochair

XSequoia Project

InfraSD Cochair

JKM Software


XCaroline RosinNIST

Agenda and Minutes

Agenda Item



Sept 2020 WGM PlanningNathan

Finalize agenda here: 2020-09 September Virtual Meeting

FHIR Conformance Usage IndicatorRobShow slides
Questions on V2Rob/Caroline
  • Questions about items in Frank's database
  • HL7 Table 0125, OBX-2/5

Items for Future Discussion

Agenda Item



Health StatusFrank

NO Update

We only responded to 3 out of 7 PSS. But what did we miss? 

Need to go back to Ann to ask about what we missed. Get an idea of what we did and what we missed. 


No update

Nathan will monitor this location for new PSS: Decisions


General Discussion on data quality. Outcome: setup demo of CDC/AIRA Data Quality and NIST qDAR tool.

Put this on agenda after the WGM. VA would be interested in this. Put this on as running item. Look to do this in October. 



GitHub repo request

  • conformance-artifacts
    • Definition: All artifacts related to conformance for all product lines. With a focus both on universal conformance concepts and conformance concepts focused on specific product lines. Would include conformance methodology, guidance, extensions, etc. 
    • Nathan Bunker Send this to Josh and ask for "conformance-artifacts"
Project Status UpdateNathan

Will discuss July 21

Projects Conformance is Sponsoring

Conformance Usage IndicatorIoana

Discuss July 14?

Reviewed version of Ioana's document that Rob sent with his comments. Some changes are being recommended:

  • Break the table out into two tables: One for Submitter requirements and the other for the Receiver requirements. 
  • Move the Multiplicity column out to it's own table. 
  • Create two new columns in the new table and break the requirements out into Implementation and Operational. Modeled after v2 work. 
  • Question about name of document "Extension" or "Extensions". We are only defining one extension at this point. 
  • Question about defining usage of resources, how would this be done? 
  • This is for interoperability implementation guides, some FHIR guides might just be informational or defining code sets. 

Discuss more next Tuesday. 

V2 Conformance WebsiteRob

Discuss later in August

On hold on this project for the summer break. Will pick it up again in August. 

Next week need to review initial content. Put up Message Conformance methodology. Start planning the hierarchy and architecture of it before we start putting everything up. Rob will demo next week. Will take small baby steps towards the vision of having an overarching methodology. Take a look and we can discuss next week. 

Data Type FlavorsRobTargeting a January ballot. NIST tooling now is supporting data type flavors, and Rob is working on this more. Rob will circle back and involve Craig for an initial review and then will be shared with Conformance. 
Message Structures questionRobFor example a message structure ORU^R01, but they need an additional segment for a new guide. Rename the structure id? Or go back and get a new structure id? How do we handle that? The profile id indicates the definitive structure. A way to think about this: the profile id really is the overriding indication of the message structure. This guidance can go into the conformance methodology section. 

Discussion for next time: Table 396 Need to come to a resolution as a group. 

Nathan Bunker Will look and notes and bring this back for the agenda. 

  • No labels