Stream: smart/scheduling-links
Topic: Does file order matter in the manifest?
Cooper Thompson (Mar 11 2021 at 17:35):
For the smart scheduling links spec, does or should the order of files matter? Specifically, should all Location files come first, then all Schedule, then all Slot? or can you do groups of Location/Schedule/Slot? I think from the spec the order isn't specified, I just don't know if some clients might have a strong preference for them to be ordered by resource type.
Josh Mandel (Mar 11 2021 at 18:38):
The order of files shouldn't matter; expectation is that clients can tell the types, and can fetch in any order they want (and clients understand that Slots depend on Schedules which depend on Locations).
@Cooper Thompson does this make sense, and would you want explicit language to this effect?
Cooper Thompson (Mar 11 2021 at 19:07):
That does make sense, I was just double checking. My opinions are in constant turmoil as I move between the highly capable folks in the FHIR community and the naïve (or hurried) app developers that are just trying to get code out the door and don't fully digest the implicit assumptions in specs.
Since this is a targeted use case (for now), I'm going to believe we don't need language. And really, adding more language like that just makes the spec longer and means it's more likely to be skimmed over.
Last updated: Apr 12 2022 at 19:14 UTC
