New Zealand Rheumatic Fever FHIR Implementation Guide
0.4.7 - draft

New Zealand Rheumatic Fever FHIR Implementation Guide - Local Development build (v0.4.7) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Rheumatic Fever Data Models

FHIR data models (pilot phase)

This section provides an overview of the design of the FHIR data representations that authorized applications can use to record and interchange rheumatic fever information.

FHIR resource model

Rheumatic fever FHIR resource data model Rheumatic fever FHIR interchangeable data «FHIR R4B»:APPOINTMENTRepresents planned encounters.In a typical RF appointment, a patientwill get preventative medication(secondary prophylaxis).text: appointment descriptionstatus:#booked | #arrivedserviceCategory $sct#58718002"Rheumatic fever (disorder)"serviceType$sct#360271000 "Prophylaxis"$sct#772071006 "Referral to dentist"..start: instant (UTC)end: instance (UTC)participant: Reference(Practitioner) «RF profile»:CAREPLANCaptures patient planned medicationand next appointmentidentifier[NHI] (official): NHIidentifier[case] (usual): case Id (salesforce)category: $sct#320721000210102"Rheumatic fever secondary prevention care plan"onHoldReason: stringclosureReason: stringlifelongSecondaryProphylaxis: booleanextensions «RF profile»:PATIENTCaptures patient registration detailExtends NzPatient to represent whanaucare roleplayers.identifier[NHI] (official): NHIname: HumanNamebirthDate: dategender: codetelecom: ContactPoint[]address: Address[]ethnicity 0..*: code[]nzCitizen: codepatient.contact[].whanauMemberCareRole: CodingwhanauMemberCareRelationship: stringwhanauMemberCarePrimary: booleaninterpreterRequired: boolean(extensions) «RF profile»:CARETEAMTeams of RF secondary preventionparticipants (practitioners,providers)category:$sct320741000210108"Secondary Prophylaxis Team"participant[].role «FHIR R4B»:CONSENTRepresents patient consent or opt-outfor treatment | data sharing.status:#proposed | activescope:#patient-privacy | #treatmentdateTime: dateprovision: ..period: date rangepolicy: uri «RF profile»:CONDITIONSummery of RF patient condition.Profile extends NzRFCOND (NZ Base)identifier: RFCCS condition idcategory:$sct#58718002"Rheumatic fever (disorder)"code: SNOMED diagnosis codeseverity:#Mild|Moderate|SevereclinicalStatus: #active etc.recordedDate: daterhdSeverity: code (bound)diagnosticCertainty: code (bound)assessmentDate: date (UTC)symptomaticAtDiagnosis: code (bound)extensions «FHIR R4B»:MEDICATIONcode: SNOMED (brand)ingredient: SNOMED (type) «RF profile»:MEDICATIONREQUESTMedication that is planned for RF preventionstatus: codemedicationRequestStatusintent:#planauthoredOn: dateTime (UTC)validityPeriod: dateTime (UTC)dosageInstruction:route: SNOMEDsite: SNOMEDdoseAndRateadditionalInstruction: SNOMED [frequency]medicationFrequency: code (bound)extensions «RF profile»RF diagnosis group:OBSERVATIONContains diagnostic detaileg. Jones Criteriaidentifier: RFCCS obseervation idstatus:#finalcode: SNOMEDeffectiveDateTime: datetimecomponents 0..*code: SNOMEDvalue[x]: ..dataAbsentReason: codeinterpretation: code «FHIR R4B»:MEDICATIONSTATEMENT1) Detail of benzathine given.2) Strength of lignocaine given.status:#completedcategory:$sct#58718002"Rheumatic fever (disorder)"effectiveDatePeriod: UTC dateTimenote: brand of benzathine used «FHIR R4B»:QUESTIONNAIRE(definitional)Canonical instances covering:Medication AllergiesMedications and Follow-up Planning GuidancePatient Goals and PreferencesSecondary Prophylaxis Health Assessment «FHIR R4B»:QUESTIONNAIRERESPONSECollects form data itemsas defined by a Questionnairevalue[x]: item[].answer «FHIR R4B»:ENCOUNTERContext of patient's secondary prophylaxis treatment.status:#finishedtype:$sct#58718002"Rheumatic fever (disorder)"serviceType $sct#360271000 "Prophylaxis"participant[]: Reference[Patient, Practitioner]period: datetime rangelocation: Ref(HPI facility) «FHIR R4B»:ENCOUNTERContext of patient's diagnosistype:$sct#58718002"Rheumatic fever (disorder)"location: facility / home / school «external data»RFCCS (Salesforce)Salesforce logical reflogical id: CarePlanId «external data»EpisurvNotifiable disease surveillancelogical id: Episurv number «logical ref»Patient (NHI)logical id: NHI «logical ref»HPIlogical identifier formats:NNXXXX-practitioner CPNsGXXNNN-CHPI Org Id - orgsFXXNNN-CHPI Facility Id - locs <>.supportingInformation1.appointment1 .addresses <>.supportingInfobasedOn 1 .activity.referencebasedOn .Identifier[NationalSystem]1 .careTeam .activity.reference CarePlan.authoridentifies Lead Provider .subject1 .Identifier[NationalSystem]1 *.evidence[].detail .basedOn .encounter1 .patient1 .performer1 .serviceProvider1 .medication[x]1 .requester1 .subject1 ".context"11 .basedOn .medicationReference1 .hasMember .encounter   .questionnaire .Identifier[NHI]1Notes- Model of data types (FHIR resources) and relations (FHIR references) for national rheumatic fever FHIR data.- Only attributes which are keying/defining are shown.- Arrows show direction of FHIR reference.- Solid/open dots indicate mandatory/optional data elements.-element:valueindicates element and value which scopes RF data access (SMART scopes) Key to resource type colourcolourstereotype ghost whiteStandard FHIR resource in TWO Shared Care API salmonProfiled FHIR resource orange redCanonical shared resource defined by TWO sky blueLogical identifier reference to records in other national systemsHealth NZ/Te Whatu Ora FHIR data model re-generated 08/08/2024


FHIR careplan instance lifecycle

Typical sequence of rheumatic fever FHIR resource instance creation patient registration care plan setup Medication planning Secondary prophylaxis activity recording ongoing care coordinationConsentcreated and linkedConsentCarePlan ->#draftInitial diagnosis completedCondition (updated)CareTeam definedCareTeamAllergies recordedQuestionnaire type AResponseMedications & Follow-upGuidance capturedQuestionnaire type BResponsePatient / WhanauGoals & PrefsrecordedQuestionnaire type CResponsewhen all parts readyPlan a period of medication (say2023)MedicationRequest 2023Medication (Benzathine)Medication planned for a sufficient periodat a set frequency (say every 28 days)Book appointmentsAppointment(planned encounter)July 11#bookedAppointment(planned encounter)August 8 2023#bookedAppointment(planned encounter)Sept. 5 2023#bookedmore appointments...MedicationRequest ->#active & SP/follow-up appointments bookedFirst appointment data capture (sayAugust 2023)MedicationStatement (aug)Questionnaire type DResponse (aug)Encounter ofaug appointmentAppointment (aug)->#fulfilledSecond appointment data capture (saySeptember 2023)MedicationStatement (sept)Questionnaire type DResponse (sept)Encounter ofsept appointmentAppointment (sept)->#fulfilledSimilar further instance sets ...FHIR resources accumulateas rheumatic fever patientcare continues.CarePlan#activeCarePlan#on-holdCarePlan cancelled (#revoked)CarePlan closed (#completed)NzPatient created/updatedNzPatientCarePlancreatedCarePlanConditionOn registration, CarePlan moves into#draftstate.Other sector health applications can interpret from thisthat a patient is "registered" with an NZ RF SecondaryPrevention Service.CarePlan ->#active Patient not registered /no FHIR records. Patient has an existing FHIR representation. ok ok ok Health NZ/Te Whatu Ora. Generated from PlantUML source on 08/08/2024


Secondary prophylaxis medication planning and encounter recording

Secondary prophylaxis medication planning and recording instance model Activity resources in the CarePlan«RF profile»:MEDICATIONREQUESTplanned Benzathine med.text: "Benzathine medication plan 2023"status:#activemedicationReference: Ref(benzathine medication)dosageInstruction-route:SNOMED-site:SNOMED-additionalInstruction [frequency]-doseAndRate:Dosageperformer: Ref(Practitioner)validityPeriod: eg.2023-01 to 2023-12medicationFrequency:Every twenty eight days- extension -«FHIR R4B»:MEDICATIONREQUESTplanned pain relieftext: "Lignocaine at 1% strength"status:#activemedicationCodeableConcept: NZMTdosageInstruction.doseAndRate: DosagevalidityPeriod: {same period as Benzathine plan}August 2023 (latest) appointment:APPOINTMENTidentifier: type #salesforce-careplanactivity-idstatus:#fulfilledstart:2023-08-08T00:00:00ZserviceType$sct#360271000 "Prophylaxis"supportingInfo: service provider Ref(HPI org)participant: Reference(Practitioner)next appointment (planned encounter):APPOINTMENTidentifier: type #salesforce-careplanactivity-idstatus:#bookedstart:2023-09-05T00:00:00ZserviceType$sct#360271000 "Prophylaxis"supportingInfo: service provider Ref(HPI org)participant: Reference(Practitioner)August 2023 encounter:ENCOUNTERidentifier: type #salesforce-clinicalencounter-idstatus:#finishedclass:#AMBserviceType$sct#360271000 "Prophylaxis"period.start:2023-08-08T00:00:00Zparticipant: Ref(Practitioner)serviceProvider: Ref(Organisation)August 2023 benzathine given:MEDICATIONSTATEMENTstatus:#completedeffectiveDateTime:2023-08-08T00:00:00Zdosage: Dosage// actual dose quantity,site,routeAugust 2023 pain relief given:MEDICATIONSTATEMENTstatus:#completedeffectiveDateTime:2023-08-08T00:00:00Zdosage: Dosage// actual dose quantity,site,routehealth assessment responses:QUESTIONNAIRERESPONSEquestionnaire: Canonical(SPHA)status:#completedauthored:2023-08-08T00:00:00Zitem.*: responsesbenzathine:MEDICATIONPlanned secondary prophylaxismedication brand and ingredientbenzathine dose planned25 mgMedication route (SNOMED)#78421000-Intramuscular route#26643006-Oral route#34206005-Subcutaneous routeMedication site (SNOMED)#78333006-Ventrogluteal#206007-Dorsogluteal#1403006-Vastus lateralismedication ingredient NZMT..6105-benzathine penicillin..6107-amoxicillin..6109-penicillin VK..6100-erythromycinBenzathine brand NZMT..6108-Bicillin L-Atbc-Tardocillintbc-Lentocillinlignocaine strength NZMT1074...6105-lidocaine hydrochloride anhydrous 0.5%1074...6110-lidocaine hydrochloride anhydrous 1%1074...6101-lidocaine hydrochloride anhydrous 2%lignocaine dose planned0.5 ml contained basedOn contained .medicationCodeableConcept   .medicationCodeableConcept  .Dosage.doseAndRate context encounter supportingInfo appointment Dosage.route Dosage.site Dosage.doseAndRate medicationReference basedOn medicationReference basedOn code  ingredientThis model showsa) medication planned in a patient's care plan (including lignocaine for pain relief)b) records of medication actually administered for the patient's august encounterc) two appointments representing the finished (august) and next planned encounters Notes1) Arrows indicate direction of FHIR reference2) Object colour shading as perData Dictionarymapping.FHIR resource instance object model


Secondary prophylaxis appointment planning and recording states model

Secondary prophylaxis recording: FHIR instance lifecycles PlannedAppointmentPROPOSEDFULFILLEDCANCELLEDENTERED-IN-ERRORPatient's next SP treatment duedate is represented in FHIR by anAppointment instance in their CarePlansecondary prophylaxis treatment records Encounter MedicationStatement QuestionnaireResponseFINISHEDENTERED-IN-ERRORCOMPLETEDENTERED-IN-ERRORCOMPLETEDENTERED-IN-ERRORAfter the treatment encounter takes place, 3 more FHIR resources record the details.Typically these three instances are created directly in their terminal state. state colourmeaning lime green starting state (if applicable) orange terminal state (if applicable)Health NZ/Te Whatu Ora. Generated from PlantUML source on 08/08/2024


Other care planning and encounter recording

Follow-up appointments planning and recording (instance model) Activity resources in the CarePlanplanned DENTAL appointment:APPOINTMENTidentifier: type #salesforce-careplanactivity-id (RFCCS)status:#bookedstart:2024-07-04serviceType:#772071006| Referral to dentist (procedure)supportingInfo: dental service provider Ref(org by name)Cancelled specialist appointment:APPOINTMENTidentifier: type #salesforce-careplanactivity-id (RFCCS)status:#cancelledstart:2024-09-05serviceType:#103696004| Patient referral to specialistsupportingInfo: Specialist Ref(org by name)cancelationReason:#410543007| Did not attend (qualifier value)Completed ECHO cardiogram encounter:APPOINTMENTidentifier: type #salesforce-careplanactivity-id (RFCCS)status:#fulfilledstart:2024-05-16serviceType:#40701008| Echocardiography (procedure)supportingInfo: cardiology specialist provider Ref(org by name)ECHO encounter:ENCOUNTERidentifier: type #salesforce-clinicalencounter-id (RFCCS)status:#finishedperiod: 2023-08-08participant: Ref(Practitioner)serviceProvider: Ref(Organisation)«FHIR R4B»Info from encounter:OBSERVATIONidentifier: type #salesforce-observation-id (RFCCS)status:#finalcode:#371541002| Provider comment report (record artifact)components 3..3 (SNOMED-coded)+notes: text+plan for next appointment: text+file uploaded: TBCService Type SNOMED#103696004-Patient referral to specialist (procedure)#40701008-Echocardiography (procedure)#772071006-Referral to dentist (procedure)#225340009-Housing assessment (procedure)#301631000210107-Provision for cultural support (procedure)#308440001-Referral to social worker (procedure)#351621000210102-Referral to sexual health service (procedure)  .supportingInfo .appointment .serviceType .serviceType .serviceType .encounterThis model shows different kinds of non-secondary-prophylaxis appointmenta) a planned dental appointmentb) a specialist appointment that was planned but was then cancelledc) a completed ECHO cardiography appt - details captured in an Encounter + Observation Notes1) Arrows indicate direction of FHIR reference2) Object colour shading as perData Dictionarymapping.FHIR resource instance object model


Enhanced diagnosis representation

Detailed diagnosis representation (instance model) Condition and diagnosis instances linked from RF CarePlan«RF profile»Summary of condition:CONDITIONidentifier (usual): code:#195528001Acute rheumatic feverseverity:#mild | #moderate | #severeclinicalStatus: #active etc.recordedDate:date of diagnosisonsetDateTime: date of condition onsetrhdSeverity: code (in dedicated ValueSet)diagnosticCertainty: code (in dedicated ValueSet)assessmentDate: date of RHD severity assess.(UTC)symptomStatusAtDiagnosis: SNOMEDextensions«FHIR R4B»context of diagnosis:ENCOUNTERTracks context of patient's diagnosis.status:#finishedclass:#AMBserviceType: context of diagnosis (SNOMED)period.start: date of diagnosisparticipant[0]: Reference[Patient]location[0]: hospital or service namelocation[1]: patient home address when diagnosedlocation[2]: school when diagnosed«RF profile»ECHO assessment:OBSERVATIONidentifier: type #salesforce-observation-id (RFCCS)status:#finaleffectiveDateTime: datetimecode: 439238004Echocardiography test interpretationcomponents 0..*+value[x]: result or measurement+dataAbsentReason: code+interpretation: code«RF profile»Jones Criteria:OBSERVATIONidentifier: type #salesforce-observation-id (RFCCS)status:#finaleffectiveDateTime: datetimecode: 447541000210107New Zealand Jones Criteria Assessmentcomponents 0..*+value[x]: result or measurement+dataAbsentReason: code+interpretation: code«RF profile»Strep primary evidence:OBSERVATIONidentifier: type #salesforce-observation-id (RFCCS)status:#finaleffectiveDateTime: datetimecode: 448011000210101Evidence of precedingStreptococcus group A infectioncomponents 0..*+value[x]: result or measurement+dataAbsentReason: code+interpretation: code«RF profile»Strep repeat testing:OBSERVATIONidentifier: type #salesforce-observation-id (RFCCS)status:#finaleffectiveDateTime: datetimecode: 448011000210101Evidence of precedingStreptococcus group A infectioncomponents 0..*+value[x]: result or measurement+dataAbsentReason: code+interpretation: codeDiagnostic context SNOMED (Encounter.serviceType)#22232009-Hospital (environment)#257585005-Clinic (environment)#365856005-Screening finding (finding)#261665006-Unknown (qualifier value)Jones criteria SNOMED#703119002-Carditis due to rheumatic fever (disorder)#200951007-Erythema marginatum in acute rheumatic fever (disorder)#11211002-Migratory polyarthritis (disorder)#165468009-Erythrocyte sedimentation rate ..#..-Other Jones criteria..careplan:CAREPLAN If diagnosis changes the patient's condition,a new version of this instance structure iscreated for the revised condition and diagnosis..addresses11..* .encounter evidence[0].detail1  evidence[1].detail1 evidence[2].detail1 At most one repeat instance per primary ObservationhasMember 1derivedFrom 0..1    .serviceType  .component.codeThis model shows how a rheumatic fever patient's condition and diagnosis are represented in FHIR. Note that multiple FHIRObservationinstances are used, each representing a logical ofsimilar diagnosis attributes. As FHIRObservationinstances MUST be coded (.code) and only SNOMED codes defined bya ValueSet will be used for this. Each Observation instance has:- An overall SNOMED code for the class of observation data points, and- All its.component[]values SNOMED-coded, and- Refers to the diagnosis encounter via its.encounterelement Notes 1) Arrows indicate direction of FHIR reference2) Object colour shading as perData Dictionarymapping.FHIR resource instance object modelHealth NZ/Te Whatu Ora. Generated from PlantUML source on 08/08/2024