Project: doctolib-doctolib · Branch: .invalid · Mode:  · Model: claude-haiku-4-5-20251001

Stats: 1 user messages, 24 tool calls, tools used: Bash, Read.

Conversation

Turn 1 — User

Search the codebase (working directory: /Users/USER/workspace/doctolib/doctolib) for any existing utility that hashes or pseudonymizes a patient identifier (INS, nationalHealthIdentifier, or similar). I'm looking for:
1. Any function that takes an INS/patient identifier and returns a hashed or anonymized version of it for logging or analytics purposes
2. Any existing pattern of sending a hashed/pseudonymized patient ID in monitoring events (sendMonitoringEvent calls)
3. Any reference to "patient_id_hash", "hashed_ins", or similar in TypeScript files

Search breadth: medium. Report exact file paths and function signatures if found. If nothing is found, say so explicitly.

Turn 1 — Assistant

I'll search the codebase for utility functions related to hashing or pseudonymizing patient identifiers. Let me start with a broad search for relevant patterns.

Tools used:

- Bash: find /Users/USER/workspace/doctolib/doctolib -type f \( -name ".ts" -o -name ".tsx" -o -name ".js" \) | head -50

Tool results:

  → result (ok): /Users/USER/workspace/doctolib/doctolib/jest.config.js
/Users/USER/workspace/doctolib/doctolib/junitProperties.js
/Users/USER/workspace/doctolib/doctolib/babel.config.js
/Users/USER/workspace/doctolib/doctolib/.prettierrc.js
/Users/USER/workspace/doctolib/doctolib/frontend-metrics.config.ts
/Users/USER/workspace/doctolib/doctolib/postcss.config.js
/Users/USER/workspace/doctolib/doctolib/stylelint.config.js
/Users/USER/workspace/doctolib/doctolib/.figmaexportrc.js
/Users/USER/workspace/doctolib/d
…(truncated, 2714 more chars)

Now let me search for patterns related to hashing, patient IDs, INS, and monitoring events:

Tools used:

- Bash: grep -r "patient_id_hash\|hashed_ins\|hashPatient\|pseudonym" /Users/USER/workspace/doctolib/doctolib --include=".ts" --include=".tsx" --include=".js" 2>/dev/null | head -20

Tool results:

  → result (ok): /Users/USER/workspace/doctolib/doctolib/app/assets/javascripts/queries/predict-exams/useInferExamsMutation.ts:import { XFeature } from 'queries/pseudonymization/useBatchPseudonymizeTextMutation'
/Users/USER/workspace/doctolib/doctolib/app/assets/javascripts/queries/pseudonymization/useBatchPseudonymizeTextMutationV2.ts:import { XFeature, type BatchPseudonymizeTextResponse } from 'queries/pseudonymization/useBatchPseudonymizeTextMutation'
/Users/USER/workspace/doctolib/doctolib/app/assets/javascr
…(truncated, 3639 more chars)

Good! I found references to pseudonymization. Let me search for INS and patient ID hashing specifically:

Tools used:

- Bash: grep -r "INS\|nationalHealthIdentifier" /Users/USER/workspace/doctolib/doctolib --include=".ts" --include=".tsx" 2>/dev/null | grep -v "node_modules" | head -30

Tool results:

  → result (ok): /Users/USER/workspace/doctolib/doctolib/app/assets/javascripts/types/doctor/api/Patient.ts:import type { InsiStatus } from '@doctolib/financial_os_api/public/types/INSi'
/Users/USER/workspace/doctolib/doctolib/app/assets/javascripts/contexts/doctor/desktop/__mocks__/EPrescriptionContext/consulterEPrescription-Response.xml.ts:          <ns15:INS>
/Users/USER/workspace/doctolib/doctolib/app/assets/javascripts/contexts/doctor/desktop/__mocks__/EPrescriptionContext/consulterEPrescription-Response.xm
…(truncated, 5207 more chars)

Let me search more specifically for hash functions and monitoring event patterns:

Tools used:

- Bash: grep -r "sendMonitoringEvent\|sha256\|hash.patient\|hashINS" /Users/USER/workspace/doctolib/doctolib --include=".ts" --include=".tsx" 2>/dev/null | grep -v "node_modules" | head -30

Tool results:

  → result (ok): /Users/USER/workspace/doctolib/doctolib/app/assets/javascripts/entrypoints-content/doctor-desktop.tsx:import { monitoringPerformanceAttributes, sendMonitoringEvent } from 'services/monitoring'
/Users/USER/workspace/doctolib/doctolib/app/assets/javascripts/entrypoints-content/doctor-desktop.tsx:          sendMonitoringEvent({
/Users/USER/workspace/doctolib/doctolib/app/assets/javascripts/entrypoints-content/doctor-desktop.tsx:const sendMonitoringEventForDidomi = () => {
/Users/USER/workspace/doct
…(truncated, 4891 more chars)

Now let me look at the monitoring service and search for patient ID hash utilities more broadly:

Tools used:

- Bash: find /Users/USER/workspace/doctolib/doctolib -type f -name "monitoring" \( -name ".ts" -o -name ".tsx" \) 2>/dev/null | grep -v node_modules

Tool results:

  → result (ok): /Users/USER/workspace/doctolib/doctolib/packages/@doctolib/monolith-mfr-tools/src/shared/datadog/send-monitoring-event.test.ts
/Users/USER/workspace/doctolib/doctolib/packages/@doctolib/monolith-mfr-tools/src/shared/datadog/module-version-monitoring.test.ts
/Users/USER/workspace/doctolib/doctolib/packages/@doctolib/monolith-mfr-tools/src/shared/datadog/send-monitoring-event.ts
/Users/USER/workspace/doctolib/doctolib/packages/@doctolib/monolith-mfr-tools/src/shared/datadog/module-version-monitori
…(truncated, 795 more chars)

Tools used:

- Read: /Users/USER/workspace/doctolib/doctolib/packages/@doctolib/monolith-mfr-tools/src/shared/datadog/send-monitoring-event.ts

Tool results:

  → result (ok): 1	import { envIsDevelopment, envIsStaging, envIsTest } from '@doctolib/variation-management/environment'
2	import { FRONTEND_MONITOR, getNewrelicEventUrl } from 'services/constants/new-relic'
3	
4	/ A named event with arbitrary key-value context to be sent to the monitoring backend. /
5	type MonitoringEvent = {
6	  / Event identifier, used as the action name in the DD Logs payload. /
7	  name: string
8	  / Arbitrary key-value pairs included in the payload. /
9	  context: Record<string, 
…(truncated, 2114 more chars)

Let me search for any utilities that specifically hash patient identifiers:

Tools used:

- Bash: find /Users/USER/workspace/doctolib/doctolib -type f \( -name "hash" -o -name "anonymiz" \) \( -name ".ts" -o -name ".tsx" \) 2>/dev/null | grep -v node_modules | head -20

Tool results:

  → result (ok): /Users/USER/workspace/doctolib/doctolib/packages/@doctolib/os_privacy_center/src/components/access_rights_tab/DeanonymizationForSupport.test.tsx
/Users/USER/workspace/doctolib/doctolib/packages/@doctolib/os_privacy_center/src/components/access_rights_tab/DeanonymizationForSupport.tsx
/Users/USER/workspace/doctolib/doctolib/packages/@doctolib/secure_messaging_core/src/services/shared/mailbox/anonymizeMailboxDebugRecord.ts
/Users/USER/workspace/doctolib/doctolib/packages/@doctolib/secure_messaging
…(truncated, 1078 more chars)

Tools used:

- Read: /Users/USER/workspace/doctolib/doctolib/packages/@doctolib/secure_messaging_core/src/services/shared/mailbox/anonymizeMailboxDebugRecord.ts

Tool results:

  → result (ok): 1	import type { AnonymizedDebugRecord, MailboxDebugRecordDecorated } from '#types/MailboxDebug'
2	
3	type AsParams = {
4	  name: string
5	  value: unknown
6	}
7	
8	const isArray = (value: unknown): value is unknown[] =>
9	  typeof value === 'string' || (typeof value === 'object' && value !== null && value !== undefined && 'length' in value)
10	
11	const isRecord = (value: unknown): value is Record<string, unknown> => typeof value === 'object' && value !== null
12	
13	type AsRootParams = Omit<AsP
…(truncated, 14138 more chars)

Now let me search more specifically for hash and crypto utilities:

Tools used:

- Bash: grep -r "crypto\|crypto-js\|blake\|md5\|sha\|hash" /Users/USER/workspace/doctolib/doctolib --include=".ts" --include=".tsx" -l 2>/dev/null | grep -v node_modules | head -30

Tool results:

  → result (ok): /Users/USER/workspace/doctolib/doctolib/app/assets/javascripts/entrypoints-content/patient-navbar.tsx
/Users/USER/workspace/doctolib/doctolib/app/assets/javascripts/entrypoints-content/doctor-desktop-providers.mock.tsx
/Users/USER/workspace/doctolib/doctolib/app/assets/javascripts/entrypoints-content/doctor-desktop.tsx
/Users/USER/workspace/doctolib/doctolib/app/assets/javascripts/entrypoints-content/configuration.tsx
/Users/USER/workspace/doctolib/doctolib/app/assets/javascripts/entrypoints-con
…(truncated, 2743 more chars)

Let me check for any utils directory that might contain hashing utilities:

Tools used:

- Bash: find /Users/USER/workspace/doctolib/doctolib -type d -name "utils" -o -name "helpers" 2>/dev/null | grep -v node_modules | head -20

Tool results:

  → result (ok): /Users/USER/workspace/doctolib/doctolib/lib/utils
/Users/USER/workspace/doctolib/doctolib/db/helpers
/Users/USER/workspace/doctolib/doctolib/lib/import/utils
/Users/USER/workspace/doctolib/doctolib/app/helpers
/Users/USER/workspace/doctolib/doctolib/test/helpers
/Users/USER/workspace/doctolib/doctolib/lib/ci/helpers
/Users/USER/workspace/doctolib/doctolib/test/test_utils/helpers
/Users/USER/workspace/doctolib/doctolib/config/bundler/helpers
/Users/USER/workspace/doctolib/doctolib/test/policies/h
…(truncated, 976 more chars)

Tools used:

- Bash: find /Users/USER/workspace/doctolib/doctolib/lib/utils -type f \( -name ".ts" -o -name ".tsx" -o -name ".rb" \) 2>/dev/null

Tool results:

  → result (ok): /Users/USER/workspace/doctolib/doctolib/lib/utils/strings.rb
/Users/USER/workspace/doctolib/doctolib/lib/utils/bsnr_lanr_format_validation.rb
/Users/USER/workspace/doctolib/doctolib/lib/utils/sql.rb
/Users/USER/workspace/doctolib/doctolib/lib/utils/translate_test_file_service.rb
/Users/USER/workspace/doctolib/doctolib/lib/utils/sort.rb

Let me search for monitoring events that include patient IDs or INS:

Tools used:

- Bash: grep -r "sendMonitoringEvent.patientId\|sendMonitoringEvent.INS\|sendMonitoringEvent.patient" /Users/USER/workspace/doctolib/doctolib --include=".ts" --include=".tsx" 2>/dev/null | head -20

Tool results:

  → result (ok): (Bash completed with no output)

Let me look at the services/monitoring directory directly:

Tools used:

- Bash: find /Users/USER/workspace/doctolib/doctolib -path "/services/monitoring" -type f \( -name ".ts" -o -name ".tsx" \) 2>/dev/null | grep -v node_modules

Tool results:

  → result (ok): /Users/USER/workspace/doctolib/doctolib/app/assets/javascripts/services/monitoring/index.ts
/Users/USER/workspace/doctolib/doctolib/app/assets/javascripts/services/monitoring/with-fetch.ts
/Users/USER/workspace/doctolib/doctolib/app/assets/javascripts/services/monitoring/test-helpers/frontMonitoringEventHandler.ts

Tools used:

- Read: /Users/USER/workspace/doctolib/doctolib/app/assets/javascripts/services/monitoring/index.ts

Tool results:

  → result (ok): 1	import { getUserProductLine, isEhrUser } from 'engines/ehr/services/ehr-user-helpers'
2	import { omit } from 'lodash-es'
3	import { envIsDevelopment, envIsStaging, envIsTest } from '@doctolib/variation-management/environment'
4	import { FRONTEND_MONITOR, getNewrelicEventUrl } from 'services/constants/new-relic'
5	import httpClient from 'services/http-client/doctor/desktop/httpClient'
6	import  as Storage from 'services/storage/Storage'
7	import type { Window } from 'static/rum-datadog/rum-dat
…(truncated, 2071 more chars)

Let me search for any existing function that creates a hash or pseudonymization of patient IDs:

Tools used:

- Bash: grep -r "patientId\|patient_id" /Users/USER/workspace/doctolib/doctolib --include=".ts" --include=".tsx" 2>/dev/null | grep -i "hash\|crypt\|sha\|pseudonym" | head -20

Tool results:

  → result (ok): /Users/USER/workspace/doctolib/doctolib/app/assets/javascripts/types/doctor/consultation/test-helpers/SharedDocumentFixtureBuilder.ts:      patient_id: '986223649',
/Users/USER/workspace/doctolib/doctolib/app/assets/javascripts/types/doctor/consultation/test-helpers/SharedDocumentFixtureBuilder.ts:      patient_id: '986223649',
/Users/USER/workspace/doctolib/doctolib/app/assets/javascripts/types/doctor/api/SharedDocument.ts:    patient_id: string
/Users/USER/workspace/doctolib/doctolib/app/asset
…(truncated, 3730 more chars)

Let me check for any crypto or hash packages in package.json:

Tools used:

- Bash: grep -r "crypto\|sha\|blake\|md5\|hash" /Users/USER/workspace/doctolib/doctolib/package.json /Users/USER/workspace/doctolib/doctolib/packages//package.json 2>/dev/null | head -20

Tool results:

  → result (ok): /Users/USER/workspace/doctolib/doctolib/package.json:    "postbuild": "node config/bundler/rspack/fix-template-strings.js && node config/bundler/shared/validate-manifest.js",
/Users/USER/workspace/doctolib/doctolib/package.json:    "@doctolib/ehr-shared": "^2.33.0",
/Users/USER/workspace/doctolib/doctolib/package.json:    "@tanker/crypto": "^4.3.0",
/Users/USER/workspace/doctolib/doctolib/package.json:    "crypto-browserify": "3.12.0",
/Users/USER/workspace/doctolib/doctolib/package.json:    "sh
…(truncated, 15 more chars)

Good! Let me search for actual usage of crypto functions:

Tools used:

- Bash: grep -r "@tanker/crypto\|crypto-browserify" /Users/USER/workspace/doctolib/doctolib --include=".ts" --include=".tsx" 2>/dev/null | grep -v node_modules | head -30

Tool results:

  → result (ok): /Users/USER/workspace/doctolib/doctolib/app/assets/javascripts/components/doctor/desktop/pages/patient/patient-file-tabs/consultation/TreatmentPlan/DocumentPreview/de/KbvDocuments/hooks/usePatientFields.test.tsx:jest.mock('@tanker/crypto')
/Users/USER/workspace/doctolib/doctolib/app/assets/javascripts/components/doctor/desktop/pages/patient/patient-file-tabs/profile/InsuranceProfile/InsuranceProfile.test.tsx:jest.mock('@tanker/crypto')
/Users/USER/workspace/doctolib/doctolib/engines/cdar2/app/as
…(truncated, 4794 more chars)

Let me look at one of the actual crypto usages:

Tools used:

- Read: /Users/USER/workspace/doctolib/doctolib/packages/@doctolib/task-manager/src/shared/hooks/data-capture/useTaskDataCapture/useTaskAssigneeCapture.ts

Tool results:

  → result (ok): 1	import type { Account } from '#types/attribute'
2	import { AccountTypes } from 'monolith_DEPRECATED/types/api/Account'
3	// @ts-expect-error no type found for this package
4	import crypto from 'crypto-browserify'
5	import isTelesecretary from '#utils/isTelesecretary'
6	import useAccount from 'monolith_DEPRECATED/hooks/doctor/useAccount'
7	import { useCallback, useMemo } from 'react'
8	import { useLocalStorage } from 'monolith_DEPRECATED/services/storage/Storage'
9	
10	export interface Captured
…(truncated, 1802 more chars)

Great! Now let me search specifically for any hash functions related to patient identifiers:

Tools used:

- Bash: grep -r "createHash\|createHmac" /Users/USER/workspace/doctolib/doctolib --include=".ts" --include=".tsx" 2>/dev/null | grep -v node_modules | grep -v ".test\|.spec"

Tool results:

  → result (ok): /Users/USER/workspace/doctolib/doctolib/engines/cdar2/app/assets/javascripts/components/doctor/desktop/MetadataExtrinsicObject.ts:export const createHash = (file: string): string => crypto.createHash('sha1').update(file).digest('hex')
/Users/USER/workspace/doctolib/doctolib/engines/cdar2/app/assets/javascripts/components/doctor/desktop/MetadataExtrinsicObject.ts:  ValueList: [{ Value: createHash(cda) }],
/Users/USER/workspace/doctolib/doctolib/packages/@doctolib/welcome-process/src/de-welcome-pr
…(truncated, 2924 more chars)

Excellent! Let me look at the createHash helper in the welcome-process package:

Tools used:

- Read: /Users/USER/workspace/doctolib/doctolib/packages/@doctolib/welcome-process/src/de-welcome-process/helpers/createHash.ts

Tool results:

  → result (ok): 1	import { v5 as uuidv5 } from 'uuid'
2	
3	export const createHash = (identifier: string | null | undefined): string => {
4	  if (!identifier) {
5	    return ''
6	  }
7	
8	  return uuidv5(identifier, uuidv5.URL)
9	}
10

Now let me check that useFindBestGuessAssociation file to see how it's used:

Tools used:

- Read: /Users/USER/workspace/doctolib/doctolib/packages/@doctolib/welcome-process/src/de-welcome-process/components/modals/PreAssociationModal/useFindBestGuessOrConfirmedAssociation/useFindBestGuessAssociation.ts

Tool results:

  → result (ok): 1	import { useQuery } from '@tanstack/react-query-v5'
2	import httpClient from 'monolith_DEPRECATED/services/http-client/doctor/desktop/httpClient'
3	import type { Patient } from 'monolith_DEPRECATED/types/doctor/api/Patient'
4	import type { DeHealthCardBeneficiary } from '@doctolib/de_public_billing/public/health-card/DeHealthCardBeneficiary'
5	import { searchCostBearerPlanQuarterlyRecord } from '@doctolib/cost-bearer-plan/searchCostBearerPlanQuarterlyRecord'
6	import type { PotentialAssociatio
…(truncated, 2092 more chars)

Let me look at the MetadataExtrinsicObject to see how the hash is used there:

Tools used:

- Read: /Users/USER/workspace/doctolib/doctolib/engines/cdar2/app/assets/javascripts/components/doctor/desktop/MetadataExtrinsicObject.ts

Tool results:

  → result (ok): 1	import dayjs from 'dayjs'
2	// @ts-expect-error no type found for this package
3	import crypto from 'crypto-browserify'
4	import { v4 as uuidv4 } from 'uuid'
5	import type { DocumentationOf } from 'engines/cdar2/types/DocumentationOf'
6	import type { Code, Time } from 'engines/cdar2/types/cdaTypes'
7	import { GROUP_PRACTICE } from 'engines/cdar2/types/ComponentOf'
8	import { parse } from 'engines/cdar2/components/doctor/desktop/CdaGenerator'
9	import type { ClinicalDocument } from 'engines/cda
…(truncated, 13937 more chars)

Let me now search for any monitoring calls that include identifiers to understand the pattern better:

Tools used:

- Bash: grep -r "sendMonitoringEvent.patient\|sendMonitoringEvent.id\|sendMonitoringEvent.identifier" /Users/USER/workspace/doctolib/doctolib --include=".ts" --include=".tsx" -A 3 2>/dev/null | head
…(truncated, 4 more chars)

Tool results:

  → result (ok): /Users/USER/workspace/doctolib/doctolib/app/assets/javascripts/entrypoints-content/doctor-desktop.tsx:const sendMonitoringEventForDidomi = () => {
/Users/USER/workspace/doctolib/doctolib/app/assets/javascripts/entrypoints-content/doctor-desktop.tsx:  sendMonitoringEvent({ name: 'didomi_notice_shown', details: {} })
/Users/USER/workspace/doctolib/doctolib/app/assets/javascripts/entrypoints-content/doctor-desktop.tsx:  delete window.sendMonitoringEventForDidomi
/Users/USER/workspace/doctolib/docto
…(truncated, 2226 more chars)

Let me search for other monitoring events to see the pattern better:

Tools used:

- Bash: grep -r "sendMonitoringEvent" /Users/USER/workspace/doctolib/doctolib --include=".ts" --include=".tsx" -B 2 -A 2 2>/dev/null | grep -v node_modules | grep -v ".test\|.spec" | head -80

Tool results:

  → result (ok): /Users/USER/workspace/doctolib/doctolib/app/assets/javascripts/entrypoints-content/doctor-desktop.tsx-import i18n from 'services/i18n'
/Users/USER/workspace/doctolib/doctolib/app/assets/javascripts/entrypoints-content/doctor-desktop.tsx-import { initializePageReloadOnNewRollout } from 'services/browser/page-reloader'
/Users/USER/workspace/doctolib/doctolib/app/assets/javascripts/entrypoints-content/doctor-desktop.tsx:import { monitoringPerformanceAttributes, sendMonitoringEvent } from 'services/
…(truncated, 11135 more chars)

Perfect! Now I have a comprehensive picture. Let me create a summary of my findings.

Summary of Findings

Based on my search of the codebase, here are my findings regarding utilities for hashing or pseudonymizing patient identifiers:

1. Existing Hash/Pseudonymization Utilities Found

a) UUIDv5-based Hash (Welcome Process)
File: /Users/USER/workspace/doctolib/doctolib/packages/@doctolib/welcome-process/src/de-welcome-process/helpers/createHash.ts

import { v5 as uuidv5 } from 'uuid'

export const createHash = (identifier: string | null | undefined): string => {
  if (!identifier) {
    return ''
  }

  return uuidv5(identifier, uuidv5.URL)
}

Usage: Used in /Users/USER/workspace/doctolib/doctolib/packages/@doctolib/welcome-process/src/de-welcome-process/components/modals/PreAssociationModal/useFindBestGuessOrConfirmedAssociation/useFindBestGuessAssociation.ts to hash beneficiary identifiers for React Query cache keys.

b) SHA-1 Hash (CDA Documents)
File: /Users/USER/workspace/doctolib/doctolib/engines/cdar2/app/assets/javascripts/components/doctor/desktop/MetadataExtrinsicObject.ts (line 35)

export const createHash = (file: string): string => 
  crypto.createHash('sha1').update(file).digest('hex')

Usage: Used for hashing CDA document content, not patient identifiers specifically.

c) MD5 Hashes for User Tracking
Several locations use MD5 hashing for account IDs in local storage keys (not patient IDs):
- /Users/USER/workspace/doctolib/doctolib/packages/@doctolib/task-manager/src/shared/hooks/data-capture/useTaskDataCapture/useTaskAssigneeCapture.ts (line 28)
- /Users/USER/workspace/doctolib/doctolib/packages/@doctolib/task-manager/src/hooks/useCounterCookie.ts
- /Users/USER/workspace/doctolib/doctolib/packages/@doctolib/siilo_ui/src/contexts/SiiloWebContext/SiiloWebContextProvider.tsx

2. Monitoring Event Service

File: /Users/USER/workspace/doctolib/doctolib/app/assets/javascripts/services/monitoring/index.ts

The sendMonitoringEvent function accepts arbitrary details but currently does NOT include hashed patient IDs. It includes:
- doctolib_account_id (user/account ID, not patient ID)
- Performance metrics
- Event names and arbitrary details

3. No Patient ID Hash Pattern in Monitoring Events

After searching for patterns like sendMonitoringEvent.patientId, sendMonitoringEvent.*INS, etc., I found NO existing pattern of sending hashed or pseudonymized patient IDs in monitoring events.

4. INS References

INS (French health identifier) is referenced in:
- /Users/USER/workspace/doctolib/doctolib/engines/cdar2/app/assets/javascripts/components/doctor/desktop/MetadataExtrinsicObject.ts (line 97) - used in CDA document construction for sourcePatientId
- Mock XML test data for ePrescription

But there is no existing utility function that hashes INS values.

5. Crypto Packages Available

- @tanker/crypto (v4.3.0)
- crypto-browserify (3.12.0)

Both are available in the project but are primarily used for encryption/decryption, not hashing patient IDs.

Conclusion

NO existing utility function for hashing or pseudonymizing patient identifiers (INS, nationalHealthIdentifier, or patientId) for logging or analytics purposes was found. The codebase has:
- A UUIDv5-based hash utility (but for beneficiary identifiers in cache keys)
- SHA-1 and MD5 hashing utilities (but for document content and user account IDs)
- A monitoring event service (but without patient ID hashing patterns)

You would need to create a new utility if you want to add hashed patient ID support to monitoring events.