SDWGMinutes(AttendanceSheetsatBottom)

MondayQ1 MEETING

AgendaReviewCompleted–9:19AM

Appointanactingco-chairmotiontoacceptCoreySpearsforSDWG.MadebyCalvin,SecondRick,Against:0Abstain:0For:UnanimousMotionpassesAnnouncementsUpdateoncurrentballot-numberofcommentsandplannedballotreconciliationUpcomingballots–

HAI–willbedoinganSTUupdate.MotiontoaccepttheHAIrevisionsbeaDSTUUpdate.Sarah,Gay–Abstain:3Against:0For:19MotionpassesUpdateSDWG3YearPlanCommitteereviewoftheSDWG3yearplan-Austin

SWOT–updatesReviewPBSmetricsandworkgrouphealthExpiringStandardsMOTIONTOCLOSETHEFOLLOWINGPROJECTS(679,568,487)MadeRick,CoreyOpposed:0Abstains:0For:Unanimous-MotionpassesKeithPertinate…–updateWikiProject-updateAgingProjects/document

381-PatientAssessments–isontheexpiredDSTUpage

Wewillcoversomeoftheseitems,onacall.

Motion:QuestionnaireF0rmDefinitionandQuestionnaireResponse(335,336)toextendtheDSTUfor1year–Madeby:Martin,SecondLisaOpposed:0Abstain:2For:19-Publicationrequestform:Austin/Martin

Q2 MEETING

(796)PatientEducationSummaryCDADocuments–willbecancelled.MotiontoclosewasmadeandapprovedunanimouslyOpposed;0Abstain:0for:UnanimousBy:Second:

PACPUpdate-20minutes-LNelsonJan2016ballot–239commentsVotetoapproveforpublishingonJune2ndUtilizedinheritanceforConformancetoothertemplates.3newentrytemplates

• PersonalGoal• PersonalPreference• Priorities–newsdtc:priorityNumber

ValueSetsextended-LOINCcodeswillbeissued,needVSACtoloadthenewLOINCcodeversionforvaluesets.Reviewswillbeupcoming–refertothemembersonlypageforIG.Publishon7/1C-CDAProductLineStrategy(A.Kreisler)

• ODH-• UDI-• PatientCareChangesC-CDA-• PharmacyModelchangestoC-CDA-

AustinpresentedaC-CDAProductLineStrategy:Whatisthenextstep?SDUUpdateProcess-forsmallchanges/largechangestoC-CDAMergingnewcontentintoC-CDANewtemplates–bebackwards/forwardscompatiblewithcurrentC-CDArelease

Volume3–accepts“optional”contentAllthecontentisoptional

Processoutline-refertoAustin’spresentation

• PSSw/StructuredDocumentsasSponsor

• DraftforCommentBallot• ThetemplatescanbeaddedtoVolume3

MustwaitatleastoneC-CDAdotreleasecycleShouldbeevidenceofimplementationsAddnewtemplatesReplacementtemplatesBreakingchangetemplatesDiagramoutlineshowtoprogresscontentintoC-CDA

ConsidertheentrypointintothespecificationstackOneperson’salternativemaybeperceivedasreplacing.Howwillthevalidatorsworkwhenthereisavolume3?DocumentLevelTemplatesmayneedsomeclarificationAddthedefinitionofwhatisbreakingchangesSendtoAustin

Q3 MEETING

Relevant&PertinentUpdatePresentationfromtheRelevantandPertinentbyRobertDieterle,HollyMillerMD,RusselLeftwich,MD.

UpdateonPharmacistCarePlan(ShellySpiro)(20minutes)ExecutiveDirector–PharmacyHealthInformationTechnologyCollaborativePharmacistwhoprovidespatientcarewhowanttoincorporatetheirinformationintoHealthITStandards.PharmacistCarePlanProjectScopeStatementValuebasedpaymentscreatesaneedtodocumentintotheCarePlanthisinformationaboutpatientmedications.Theyhad4usecasesforreference.ContractedwithLantana.Theyareshort

offundingandtheyareattemptingtosecurefunding.TheyarelookingatusingtheHL7eCarePantemplate.

NeedtoplacethePharmacistCarePlanprojectonhold.TheVAisinterestedinintegrating,buthas50stateimplementations.OverviewofCDAProductFamilyStrategy(AKreisler)

http://wiki.hl7.org/index.php?title=Relevant_and_Pertinent

AustinpresentedapresentationabouttheestablishmentofaCDAproductfamily Q4 HOSTPHER–PublicHealthandEmergencyResponse

ReviewofJointprojectswithPHERSTUCommentsNationalHealthcareSurveyCDAEpicComments919thereisaneedtochangeguarantors[0..1]to[0..*]MakecommentinC-CDAR2.0andCDAR2.1tochangethis.917ImmunizationsErrata–ProcessingOverviewofC-CDAProductLinestrategyforPHER(AKreisler)

Tuesday Q1 JOINTwithCQI(CQIHosting) AlignmentofC-CDAandQRDA UpdateonCDAR2.1 ArethereanyissueswithC-CDAandQRDA WhatisQRDAbasedon?C-CDAR2.0orC-CDAR2.1

Thelastupdate,QRDAwasalignedwithC-CDAR2.1,butiftherewereanyissues,pleaseletusknow.

SDWGActionItem:WemightwanttodoareviewanyoftheErratafromAnneHarrisonC-CDAR2.1foundontheC-CDAR2.1DSTUCommentPage.

Shouldthesdtc:valueSetsallergies–doweneedtocalloutvaluesetswhichwereusedintheinstance.Itisapossiblecapability,butdoesitaddvalue? HowdodealwithProvenance Doingpatientengagement/Providers(Physiciansvs.Nursing) Source/Recorder Wantingtokeepthesourceofdataincorporatedintodocumentinstances. Source–theoriginalauthoroftheclinicalcontent. Patient,whichproviderclass(Physician/Nurse)

DataProvenance–Therehavebeeneffortsmadeinpast,buttheuptakehasnotbeengenerallygood.LookatthestandardscommitteetaskforcerecommendationsCBCChaspublishedguidanceonProvence.Theissueofengineering.HITStandardsCommittee–constrainingtheCBCCworktoasmallerset.ClinicalQualityFramework–maybeaplacetopilotthesecapabilities.Negation–ThereissomethingindicatedintheguidelinebutI’mnotgoingtodoit.QDM–logicDecisionSupport–needaclearmeanstoidentifywhysomethingisnotbeingdone,thatshouldCQL–whatworksbestwithvendorsActionNegationValueNegationCIMIdatamodels

Lookingatthisattheimplementerprospective.Needbothvendorsandmodelingtogethertoensurethatwehandlethis.Thereareexistingusecasesouttheretodayandworkingonsolutions.Q2 JOINTwithVocab(VocabHOSTING)

VSACValuesetmanagementLNelsonFormallydetermineaprocesstobeimplementedObtainanupdateontheVSACvaluesetloading.–LisaNelson.Isthereawayforthestewardtomaintainthevaluesets.Whereisthesourceoftruthtobefound.Startedtheprocessawhileago.Therearetwoversions:C-CDA1.1–valuesetcontent–arangeofcodesystemsSupportformeaningfuluse.Ayearago,therearetwomainroadblocks1.Notallthevaluesetsareavailable2.Someofthevaluesetsarelarge(100,000+)valuesWithinanumberofweekstobeingabletocreatethelargevaluesetsforR1.1

Therearetwoviews–Authors–havetwoUsers–haveoneTheusersideofthedatabasedoesnotsupportalloftheAPisButtherewillbeadownloadpage,whichwouldallowsyoutodownload

pageonVSAC.Thevaluesetmetadatawillbethere,butthelargecodesystemsthatare

available.WhichcodesSystemsnotavailable-??

LisawearemakingvaluesetsonCodeSystemsthatarechanging,somecodesareobsolete.ONC/CMS/NLM–problemabouthowtofixthisproblem.ThereisaneedtofigureouthowtomanagethevaluesetsontheNLMsolution.ThequalitycommunityhaslandedonSTATICvaluesets.DoesVSACneedanMOUwithHL7?Aquestionwasraisedtoprovidesupportfortheneedandusecasedwiththefederalcommunities.UpdateonBindingsyntaxFHIR–ifyouaregoingtodoabinding,V3supportsaconceptdomain,whichmaynotbetrackable.Bindingmustspecifythefollowing:Thespecificsetofcodesinanexpansionset.Itexiststoprovideclearguidanceonhowtobuildanimplementation.Tosupportconformancetestableimplementations.Youmustspecifyonasetofcodesthatcan

• Whatthosearesendingcando,• Whatthosewhoreceivecando• Whatderivedspecsbasedonthisspeccando.

Someissues–V2/FHIRhaveaneedtouseforDSTUcommentondeprecated986LOINCcode

Wewilllookatusingthissyntax,defineitintheCDAR2.1Specbutmayneedtokeeptheconstrainslooseinordertoremainbackwardscompatible.CDAProductFamilyStrategy(AKreisler/CBeebe) AustinprovidedareviewoftheideaofcreatingaCDAProductFamily. Assoonasyoutaskaboutsomething,youarevolunteered.Q3 HOSTPublishing/Tooling/Templates

CDAProductFamilyStrategy(AKreisler/CBeebe)ContinuethediscussionabouttheCDAProductFamilydiscussion.AustinwillpresentthepresentationontheCDAProductFamily.Intheentry-leveltemplates,wemayneedtohavethesamepeoplethinkaboutthemodelingofentriesandresources.-CDAArtifactmethodologyandmanagementTemplateRegistrydiscussion(LNelson)HL7TemplatesRegistryBusinessProcessRequirementsAnalysisRelease1–Dec.2013Templatesworkgroup.Attachmentsworkgroup–theybroughtallthreeofthegroupstogether.Thesetoolsareopensource:MDHTTrifoliaArtDécorWhatcanwedoaboutthis?Canwereusethisinformationinthedevelopmentofthesolution.MinimumQualityCriteriaforCDAIG'sSDWGGForgeReleaseProcesshttp://www.hl7.org/documentcenter/public/wg/structure/SDWG_GForge_Release_Process.docx

Toolingneedthatisnotcurrentlyaddressed(Identificationofaneed)– Templatetooling–privileges–needtoseethestructureofhowtheconformancestatementwasputtogether. Recordasaneed–toolingrequirementsandenhancements Tooling–hasaprojectunderwaytolookatthetooling.Thehelpdesk–torecordissueswithtoolsThereshouldbeacentraltoolingsupportareatosendrequeststo.Q4 HOSTFHIR,SendRepresentativestoPatientCare

(negationandvocabdiscussion)C-CDA/FHIRConnect-a-thonreportout(RGiemer)CurrentStatus–allcompositionsectionsarecovered.GettingtheotherdocumenttypestoinheritfromUSRealmHeaderFixbasingoneprofileonanother,byGraham.CreatedC-CDAStylesheetFocusonpre-ballotreviewoftheprofilesinthebuildFall2016FHIRBallotThereareotherresourcesthatDAFdidnotinclude,thatareneededfortheC-

CDAIG.FHIRConnect-a-thonforDocumentsCreateadocumentfromDAFresourcesandgeneratecorresponding

narrative.RetrieveindividualfromaFHIRserver.ThiswasthefirsttimefordocumenttransactionssinceFHIR1.1AttachmentsPeriodontalDocumentfortheAttachmentsLookatusingStructureDefinitionforthemodelingofCDAguide.CDAgoestoaClinicalDocument–Resource(research)

FHIRRequestsHaveaprocessinplacetomanagethetrackeritemsTofigureoutthetargetsforthissummerandmaturitylevelFHIRManagementneedstoknowIfyouareplanningtocreateanewresourceslettheFHIRmanagementknow.CDAProductFamilyDiscussion

MaturityModels&BallotingforDocumentResources&ProfilesC-CDAonFHIRImplementationGuide–wouldliketogointothebuildforaballot.Whatmaturityscoreshoulditbe?Level1–readyforproductionuse Level2–connect-a-thonpasses Level3–InProductionWhatistheprocesstoincludeitintotheFHIRballot.AsanImplementationGuide…NIBwillbeusedCoreResources–CoreResources–tomoveitthrough

• Composition(2now)maywanttoconsiderqualitycriteriaattempt(3)• DocumentRef• DocumentManifest

DSTU2QATracker–needstobereviewedbytheSDWGcommittee.Composition–wasnotinthetop40inthereviewbytheindustry/implementers.TheCDALogicalModel–inFHIRspecisaresearchandunderevaluation.WewilldiscussthisonThursdaytoowntheCDALogicalModelasaproductownedbyStructuredDocuments.GrahamandCalvindiscussedtheCDAProductFamilyandFHIRProductFamilyoverlapsthatexisted.GrahamsuggestedthatwemightwanttoraisethequestionaboutproductsthatbelonginbothproductfamiliestoPLAfortheirconsideration.DiscussionaboutextensionstobeappliedtotheCompositioninmodelingtheCDAdocuments.Oneofthechallengesthatwasnotedthattherehasbeenreusablesectionssharedbetweendocuments.ThisreuseofsectionsinFHIRisnotpossible.Thequestionwasthattheabilitytocreatesub-resourcesliceprofile.Thereisgoingtobea

solution,thereisasolution.ThetoolingneedstobeupdatedtosupportthiscapabilitywithinFHIR.contentReferenceusetobeanIDandnowitisanURI.Thismakesitpossibletocreateastructuredefinitiontodefinesections.Wouldtheuseofparticipantbemademorespecific?Nowthatwecanprofile/profiles,isthereanypossibilitytoshowhowthesestringsoftemplatesrelatetoeachother.OntheFHIRProfilepage,thereisacomparisonbetweenDAFandQICore.Thistoolwillshowtheunionandtheintersection.Theyareworkingoutthecomparisontoolingtomakeitpossibletoseetherelationshipsbetweentheprofiles.Wednesday Q1 MEETING http://wiki.hl7.org/index.php?title=C-CDA:_Enhancing_Implementation_(ONC_Grant_Project)

C-CDACompanionGuideProject(JDuteau) ReviewtheC-CDACompanionGuideatfuturemeeting

BallotfortheSeptballot/publishthefinalguideinNov.2016Thisisthetimeforguidanceandwanttoprovidefeedback,nowisthetimetoprovideguidance.40Guidanceitemsnow,willaddexamplesinthedraftguide15guidanceitemsfordiscussionattheWGM5–werecarriedfromC-CDAR1.1ImplementationGuide

• MissingInformationandUseofNullFlavor–rewording(value)• AllergyDates• ProblemDates• Immunizations–ImmunizationDate,StatusCode,Refusals

GuidanceGeneratingUniquePersistentRecordIdentifiers-maintainandexportmultipleidentifierspercontentandanotherforthe

instanceofthethingShouldweaddsection.effectiveTimeasanalternateSectiontimeIntervals–IndicatingtheScopeofTimeforSectionsContent

ConsistentuseofDischargeSummaryAdmissionandDischargeDatesIntheheaderwhenyouhaveanencounter–thereisatimestampforthe

AdmissionandDischargeDates.EncounterDiagnosisgoesinEncountersActivityinEncountersSection.MedicationsinDischargeSummariesWhatdoesthemedicationsectionsmeaninthecontextinofaDischarge

SummaryCommonClinicalDataSetMedications

o Admissionso Dischargeo MedicationsAdministrated

UpdateonC-CDAImplementation-a-thon

TwomeetingswerecompletedandanotherwillbeinSept. BirthSexandGenderIdentify SocialHistory–BirthSex Administrative–M/F/Unknown ImplantedDevicesinMedicalEquipmentSection LabTestsw/andw/oresultsPlanofTreatment–asanorderResultssectionwillcontaintheorderandresultsHealthConcernsVsProblemsHealthConcerns–ImportantbytheproviderProblems–allGoals/PlanofTreatment–currentandnonecurrentQ2 MEETING

CDAInternationalPatientSummaryProjectWedQ2(RobHausam,MD)

INTERPAS–Project(lastdiscussedinParis)ONC/EUInteroperabilityInitiative,whichwasbasedonC-CDAR1.1CCDtemplateandtheepSoSIGv1.4Motion:CDAInternationalPatientSummaryProjectacceptprojectscopedocument.ByRob,SecondMotionStartingpoint–acompletedocumentbutwithtemplatesthatmightbereused.InternationalPatientSummaryvs(EU/US)MedicalITsubgroupofNATOwhathasneedsinthisarea.CouldyougetvendorsintothisprojectthatmightbesupportedbyEHRSystems.Needtolookatthestatedprojectscope.epSoShasbeencreatedforpatientcontent.IHEhasinformationaboutuniversalguidanceforIGandlocalrealmIGs.Whatarethegoalsofthisproject?Therearecrossboarderusecases.

JointballotbetweenISOandHL7. Changestothecurrentscopedocument:

• WemightwanttoincludetheInternationalCouncilandtheEUHL7Organization.

• Needtoreviewtheinterestedpartiestoseeifthecontactsarestillappropriateandinterestedinparticipating

• NeedtocheckwithCEN251• INTERPASneedstobecheckedwith• NeedtoverifythatweneedtocontactthegroupsCouldyourenametheprojectto:InternationalPatientSummary(Phase1US/EU).ThereisanEU/USMOUonthisthatweneedtoconsider.

ThereisaneedtoreviewthetextoftheMOUforthetermsoftheagreement.Needtoverifywhichversionofdocumentsareinscopetoanalyze.Considerrevisingtothedeliverablesa.)InternationalPatientSummary

Document(INTERPAS)template(s)

Therewasadiscussionaboutwhichdocumenttypes(PatientSummary,DischargeSummary,…)thatmaybeconsideredinscope.

Therewassomeconcernthatthisshouldfocusonthecriticalcareneedsof

aninternationaltravel.Thereiscriticalcareandthereismedicaltravelforcare.IfyougotoFHIR,youwillneedtocreateanumberofProfilesonFHIR.ProfessionalRecordsStandards–theauthoritativesourceofclinicalrecords

intheUKChangetoV3Document-ClinicalReviewofchangesPHMRIG(MRosner)CommentsreceivedwereaboutexamplesandcreatingtheSchematron.NeededsomehelpwithgeneratingtheSchematron.Ransomevalidationonsamples.Sentoutthelinkstothepackage(zip)onnextThursdaycall.

MinimumQualityCriteriaforCDAIGsSDWGDraftGForgeReleaseProcess

Q3 MEETING-Cancelled! Q4 MEETING,SendrepresentativetoPCWG

(Allergyandintolerance:vocabandharmonizationdiscussions)CDA2.1–diagramissues,valueset/conceptdomains/HMDissues

CDAR2.1

• CalvinBeebepresentedCDAR2.1–ACTSo Describemethodologyforreviewing/promotingattributesforthe

ClinicalStatementpatternorcoreRIMclassestoCDAR2.1.• MotiontomodifythecardinalityonlegalAuthenticatorfrom0..1to0..*

o Motion:StephanSabutscho Second:AlexanderHenketo Usecasewasmulti-disciplinaryreports.o Vote:8for,0against,0abstain,motionpasses.

• MotiontoupdatetheproseoftheCDAspecdescribingthelimitedusecaseformultiplelegalauthenticators,andalsodescribingwhennotappropriate(themajorityofthetime).

o Motion:RickGeimero Second:Viniyako Vote:8for,0against,0abstain,motionpasses.

• DiscussedchangingsomevaluesetbindingsinCDAtoconceptdomains.DoingsoforCSdatatypeswithCNEbindingswouldbreaktheschema(i.e.typeCodeelements,etc.),whereasCWEtypeswouldnot.Mostlyimpactsconfidentialitycodes.

• MotiontoreviewallCWEvaluesetstoseeiftheyshouldbecomeconceptdomains.

o Motion:Ricko Second:Viniyak/Alexandero Vote:8for,0against,0abstain,motionpasses.

• AddedsomenotestothediagramnotingareaswherethenamesdisplayedintheRMIMaredifferentfromtheXMLSchema(participant1=informationRecipient,etc.).DiscussedmaybehackingtheVisiofilebeforepublicationtofix.

• DiscussedwhattodowithcopyTime,sinceitwasdeprecatedinCDAR2.Decidedtoleaveitfornow.

• FixedsomemissingchangesfromCalvin’supdatedHMD(maxDoseQuantityshouldhavebeenupdatedtoSETwith0..*.

• DiscussedwhethertoadddefaultsforBooleanswheremissing(suchassettingisCriterionIndtofalsevs.leavingitblank).Decidedtoleaveitasisfornow.Willconsiderdiscussingitlaterwhenothermodelersarepresent.

• DiscussedaddingarelationshipbetweenObservationRangeandCriterion.Agreedneedsmorediscussion.

• DiscussedfinalupdatesregardingtotheexecutionofcompilingtheoutputoftheRMIMdesignertoHMDs,schemas,etc.

Thursday Q1 HOSTImaging,SendRepresentativesofC-CDAonFHIRprojecttoPC

IITopics–wantstodoanormativeballotofDICOMPart20–CDAforDiagnosticImagingReports.

ValidationConformanceandotherrequirements1. HL7/DICOMdiscussionsareneededtoensuretheIPissues.2. Requirementsforconformance–vocabularyrequirements

a. ImagingshoulddiscusswithVocabularyaboutcodestobeused.3. LookatmovingthenewUniversalRealmDICOMPart20C-CDADIRreport–statusofandwhatweshoulddo.BreakingChangeandauniversalrealmGForgeReleaseProcessCreatingareleasepackage–SVNwasusedtostoretechnicalartifactsIfyoucreateareleasepackage,itiseasytogetthecontentout.ConfigurationManagementProcessProposal:Cominginonalink,maypulladraft/developmentbuildSoweneedtocomeupwithareleasepackage.1. Providecommitaccessforthosewhowanttoeditartifacts2. Anyonecanproposeanewrelease(packageofcontent)

a. Shouldcontainreleasenotesforallfilesb. Shouldbezippedintoonefilec. Ifanewpackage,itmustbeaddedasanewpackage

3. Releasenumberingissimple,1.0,minor+.1,major+1.04. FillouttheAddReleaseform,fillout.5. SendanotetotheSDWGlist(copytoco-chairs)

a. 1weeknoticeb. DiscussonaStructuredDocumentsCall

Assessifanyonecanrequestanotice(e-mail),whennewpackages,releasesarecreatedinGForge? WhensomethingissettoAlphaorBetashouldtheSVNbeupdated?Q2 JOINTw/PC,Templates(PCHosting)

PCWGhostingSDWGandTemplate-Allergy/Intolerance,CarePlan,C-CDA/FHIRHarmonization,othertopicsasneeded,pleasesendreps

1.InformativeDocument–RegistryTemplatesRequirementsDocuments

Twogovernancegroups.

2.PlanforupdatingthetemplatesSTUtosharetemplates Theyhaveseveralcommentstointegrateintoit. AccepttemplatesfromTrifolia,ArtDécorandHDHT Lookingattheoverallforregistries.

RickandKiaaregoingtodoatemplatetutorial.

CDAProductFamilyStrategy-presentation ProductLineArchitecture–establishingProductFamiliesinHL7 CurrentProductFamilies–FHIR,HL72.x PlansforCDAProductFamily 1.Isacollectionofproductsthatsharecommonmethodologies,andtoolsasviewedfromthedesignprocess.ProductFamily–CDAandCDAIGsStructuredDocuments/Templates–arebothtemplatingbutwithslightdifferencesbetweensolutions.Cooperationbetweenthetoolinggroupsiswelcomed.Gov. Management MethodologyTSC CDAManagementGroup ?SGB IGPrimarySponsorWGQuestions/CommentsAttheBaltimoremeetingwewillbebringingthegroupstogethertodiscussthis ClinicalStatus–ValueSet–deprecatingproblemstatus/whatisthevaluesetrequiredfortherequirements.FHIRConcernstatuses.FHIRConcernConditionResource–theproposals–thisisatopicStructuredDocuments–Concerns&Problems–FHIRVsStructuredDocumentsHealthConcernDAM–beingworkedon.FHIR–(conditions,observations)andconcerns.NoupdateonNegation–currentstatus.Theissuesrelatedtoclarityofrequirements.Allergy/IntoleranceHarmonization–DSTUtrackedversionsarecurrentlyuptodate.

Q3 HOSTFHIR(SendarepresentativetoClinicalStatement)DiscussingballotingforC-CDAonFHIRprofilesWearecreatinganintenttoballot(NIB)andwillballotinthefall.LogicalModelofCDAinFHIR–ShouldSDWGown?WhereshoulditliveinFHIR?Wecouldpotentiallyusethisasapublicationstrategy.

Motion:HaveSDWGowntheCDALogicalModelintheFHIRpublicationpackage.AndlaterdeterminetheappropriatelocationforimplementationguidewiththeassistanceFHIRInfrastructuregroup.By:Austin,SecondGay.Opposed:0Abstain:0:For:22motionpassesValueSetQuestion–AllthevaluesetaremovingtoFHIRformatintheFHIRTerminologyServer.VocabularyvaluesetswillmovetoFHIR.GrahamindicatedthatitshouldbepossibletoidentifytheCDAIGsthathavecodesinvaluesetsthathavebeenobsoletedinIGs.VSACiscurrentlymanagingtheValueSetsforC-CDA.ThequestionaboutConceptDomains,Grahamindicatedthattheywerenotdiscussed.UpdateonHQMF

SDWGisaco-sponsorofHQMF.CQIhaspresentedaPSStomovetheHQMPtoNormative.Normativewillresolveallcommentsandlearnings.Septtarget(possibleJan)ChangethetitletoNormativeRelease1.0MotiontoapproveSDWGasaco-sponsortothePSSMadeby:Floyd,SecondPeteAgainst:0Abstain:1For:17-motionpasses.C-CDAonFHIR–therearetwoC-CDAonFHIRprojects.1124(remove)VS1122active.Q4 MEETING

C-CDAErrataProcessfromNCHSsourceIG-ReleasinganErratareleaseonR1.0/R1.1Isitinthelistoferratapackage.Onrelease2.0–asIGisbasedonC-CDAandmustdealwitherratawhen

issuesagainstC-CDA.

Problemtypevaluesets–question- C-CDAR1.1–SNOMED- C-CDAR2.0–LOINC- C-CDAR2.1–SNOMEDbase/LOINCextension- PlaceaDSTUcommentthatwechangethevaluesetidsfortheCDAR2.0

andinCDAR2.1.Filloutabugrequest!

Thelongnamesandshortnamesaremessedup.

ERRATA–shouldweproceedwithalongercycle.Iftheissuearisesaboveatypo,thenitwillbeproceed.ItwillbeagroupvotetodecidetoproceedwiththeErratapublicationingeneral.CDAProductLineeasypathAustinreviewedthecurrentprocesstoproduceareleasepackageMotion:SDWGhasidentifiedthattheProductPagedoesnotidentifywhenareleasepackagehasbeenupdated,makingitdifficulttoknowiftheerratapackagehasbeenadded.RequesttosendthisissuetoEST,LynnandCTO.MadeLisa,SecondPeteAgainst:0Abstain:0For:14motionpasses-Calvinwilltaketheaction.Openquestion:C-CDAProductLineTheODHIGbeconsideredasaprojecttoexercisetheC-CDAupdateprocessfortheproductline.Theircontentwouldcomeinasoptionalstuffandwouldnotimpacttheexistingcontent.ThecommitteetalkedabouthowtomanagetheinclusionofoptionalcontentintotheVolume3oftheC-CDApackage.Templates(excludingdocumentlevel)tobeincorporatedintovolume3aftertheyhavebeenballotedasaBallotforComment(minimum)andthenmustproceedwithaSTUUpdateprocesstogetincludedintoVolume3,whichwouldresultinanincrementtothenextminorreleases.LisaInthepurposestatementyousuggestwhereyoumightbeused.Whentheymovetobeadoptedinvolume2. FridayQ1 Jointw/Templates,PC(Templateshosting)

TBD