I agree that the design would be better with the one entity, but this is utilising an external database structure, unfortunately, and effectively trying to join two systems, hence the two tables.
I'm not trying to filter by anything, really, I just want a list of SMS messages, and the types.
The detail column in the aggregate is the service type. For Referral SMS, this could be Clinic, Scan or routine appointment. For Standard SMS, this could be Welcome SMS, advice leaflet, or something else.
I am in a position to rebuild the SMS_History entity, but this means I'd have to edit the SMS api's on the other systems, and do work on other systems too, and I'd rather avoid this if I can! It's something I'll have to do eventually though...