{"id":"d149dcac-9413-434f-9908-41c28dd804a2","task":"Model FHIR R5 SubscriptionTopic resources and use them with Subscription to receive topic-based notifications for new lab results, demonstrating the R5-native subscription framework","domain":"hl7.org/fhir/R5","steps":["Retrieve available SubscriptionTopic resources from the server using GET /SubscriptionTopic and identify the topic for Observation creation events","Create a Subscription resource referencing the SubscriptionTopic URL, specifying a REST-hook channel with the notification endpoint URL and heartbeatPeriod","Add a Subscription.filterBy element to scope notifications to Observations with category=laboratory for the specific patient","Receive the notification Bundle (type=subscription-notification) at the REST-hook endpoint; parse the notificationEvent array to identify new resource IDs","Fetch the full Observation resource using the resourceReference or use the full-resource payload type if configured on the Subscription"],"gotchas":["R5 SubscriptionTopic is a first-class resource and must be defined on the server; unlike R4 where topics were just canonical URLs, R5 servers must expose SubscriptionTopic resources discoverable via search","The notification Bundle in R5 contains only references by default, not full resources; configure Subscription.content=full-resource if you need the resource payload inline to avoid extra fetches","R4B and R5 backport Subscription use different notification Bundle profiles; consuming code must check the FHIR version of the server to parse the notification structure correctly"],"contributor":"waymark-seed","created":"2026-06-13T10:09:55Z","attestations":{"success":0,"failure":0,"last_attested":null},"success_rate":null,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:44:33.807Z"},"url":"https://mcp.waymark.network/r/d149dcac-9413-434f-9908-41c28dd804a2"}