I'm working on an update of an existing medical software and I defined user stories together with some end users. If you're not familiar with medical environments: A doctor usually has multiple patients. Each patient has multiple cases (broken leg, skin disease, etc). In medical terms, a case will be closed once the patient was treated. This might happen after a few days (illness) or sometimes weeks or months (e.g. if physiotherapy is involved). However, in most medical software, cases have to be closed after a predefined timespan (couple of days or after a month) for the billing, because most health insurances will only pay for closed cases.
The doctors in most hospitals and clinics here use a standardized form when they have a consultation with their patients, the APE Form (Annual Physical Exam).
The UI of the software is not very user friendly, therefore a big part of my work will be to improve the user experience. The UI of the cases of the current version looks very different to the APE Form and specially new doctors have troubles with the UI because of that. Therefore we want to change the UI, that it looks more like an APE Form. Now I've got the following 2 user stories and it seems that the 2nd user story is a child of the 1st one.
1st user story:
As a doctor, I expect a case in the software to look like the APE Form.
2nd user story:
As a doctor, I want to see the whole medical history in a patient case, to get a quick overview of the medical data (see attachment)
Is this correct? In all projects I've worked before, user stories were always either completly independent (means no parent) or the child of a feature. That's why I'm not sure if a user story can have another user story as a child.